Observability (Metrics, Tracing, Logging)

About this group

Description

With monitoring and observability, teams can easily share information through an organization-wide view of application and infrastructure performance and create a centralised source of operational intelligence, so your organisation can communicate and focus on quality and accountability. Metrics (what's happening) Primary form of data you send into a monitoring tool. A metric has a periodic measurement that is represented as a numerical value. The same metric can be reported from multiple sources or emitters. Typically, each unique combination of a source and a metric will result in a metric time series. Tracing (where is this hapenning) Software tracing provides developers with information useful for debugging. This information is used both during development cycles and after the release of the software. Another important consideration for software tracing is performance, specially in the microservices pattern where the complexity has increased vastly in the last years. Understanding the context and have a panoramic and detail view are equally important for root cause and performance analysis and code optimisation.(why is this happening) The extra level of detail necessary for troubleshooting, debugging, support, and auditing. As a starting point, you might find out from your metrics dashboard or alerts that a problem exists and when it started. If that’s not enough information to find the root cause, you may need to drill down deeper into the log data to see exactly what happened as the program was executing. Logs can help you debug problems even on your production systems by showing the execution path. Additionally, your support team can search for exactly what happened for each individual customer and transaction because the events are not rolled up into an aggregate. They are also great for auditing because you have a complete record for security and legal compliance.

Rules