An Introduction to O11y - ObservabilityBlog

Logs are per-application events that show you error messages and carry the voice of your applications.

To make your services "observable" you will have to collect metrics, distributed traces, and logs, better known as the three pillars of observability.

The benefits of observability?

First of all you can discover and pinpoint issues you don't know exist. Observability enables you to better pinpoint root causes of your incidents and therefore resolve them faster.

Application observability enables you to understand why your service is slow or broken and learn what needs to be done to improve performance

You learn more about your application and the code that achieves your business targets. Logs, metrics, and traces are displayed over time, and with mathematical patterns, you learn how to improve your the services you offer to your customers.

Traces are small pieces of transactions that you can group around unique business transactions. A trace is placed into multiple microservices and can be split into various pieces in the same microservice

Metrics will tell you about performances and checks. It represents most of the monitoring parts.

you will learn about issues early in the development phase. Monitoring in the early phases of the software development process lets you fix them before they impact your customer.

Monitoring means running active checks on a set of services and technical components to check their health.

O11y is an abbreviation of observability. If we take out the 11 letters between the O and the Y of observability, we get O11y. It is similar to Kubernetes and K8s.