Book Image

Implementing Azure: Putting Modern DevOps to Use

By : Florian Klaffenbach, Oliver Michalski, Markus Klein, Mohamed Waly, Namit Tanasseri, Rahul Rai
Book Image

Implementing Azure: Putting Modern DevOps to Use

By: Florian Klaffenbach, Oliver Michalski, Markus Klein, Mohamed Waly, Namit Tanasseri, Rahul Rai

Overview of this book

This Learning Path helps you understand microservices architecture and leverage various services of Microsoft Azure Service Fabric to build, deploy, and maintain highly scalable enterprise-grade applications. You will learn to select an appropriate Azure backend structure for your solutions and work with its toolkit and managed apps to share your solutions with its service catalog. As you progress through the Learning Path, you will study Azure Cloud Services, Azure-managed Kubernetes, and Azure Container Services deployment techniques. To apply all that you’ve understood, you will build an end-to-end Azure system in scalable, decoupled tiers for an industrial bakery with three business domains. Toward the end of this Learning Path, you will build another scalable architecture using Azure Service Bus topics to send orders between decoupled business domains with scalable worker roles processing these orders. By the end of this Learning Path, you will be comfortable in using development, deployment, and maintenance processes to build robust cloud solutions on Azure. This Learning Path includes content from the following Packt products: • Learn Microsoft Azure by Mohamed Wali • Implementing Azure Solutions - Second Edition by Florian Klaffenbach, Oliver Michalski, Markus Klein • Microservices with Azure by Namit Tanasseri and Rahul Rai
Table of Contents (29 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Health state


Following are the four possible states for the health of a Service Fabric entity:

  • OK: The entity and its children are healthy as of the current reports.
  • Warning: This state informs us that there may be some potential issue on this entity of any of its children. A warning state does not mean that the entity is unhealthy. Delay in communication or reporting can also cause this state. A warning state will usually recover or degrade down to an error within some time. It is normal to see this state on your cluster while you are updating the application, service, or the cluster itself.
  • Error: The entity has an error reported on it. A fix for this will be required to ensure correct functioning of this entity.
  • Unknown: This state usually shows up when the reported entity is absent in the health store. This may be because of clean up or delay in the setup.

Health policies

Health store uses policies to determine the state of an entity. These policies are called health policies. Service Fabric...