Hands-On Microservices with Kotlin

Alerting

Having that information available allows us to alert on failures or problems in our applications so we can react to that situation. And those alerts can either be visualized in our control panels or dashboards, notified to individuals or groups, or even to the system that will handle them automatically. But to do that effectively, we need to define those alerts when we create our microservices.

Try to think about these elements when you're defining your alerts:

• Have meaningful information: It is not good enough to just provide a "System Failure" message, give a context to the problem, or hints about how to handle it, for example, "Failure connecting to the customer database".
• Conditions which trigger it: Is it just because we have ...