Observability
Collect the evidence needed to understand system behavior
Observability uses metrics, logs, traces and events to help teams detect problems, understand causes and judge effects on services.
Evidence across applications and infrastructure
Metrics, logs, traces and events describe different parts of system behavior. A team needs to connect them to the same application and service context to investigate an incident or assess the effect of a change. Collecting more telemetry without a question or ownership model can increase volume without improving understanding.
Choosing useful signals
This capability supports CodeAttest work in application monitoring, performance analysis, architecture and Dynatrace. The appropriate telemetry, tools and operating practices depend on the systems and decisions in scope.
The same incident may appear as a resource change, a failed request and a user-visible symptom. Connecting those observations requires consistent service context and telemetry that can be trusted. CodeAttest examines the questions teams need to answer before deciding which signals to collect or retain, because more data alone does not guarantee better diagnosis.
Related services
This expertise supports these services: