Application observability

As explained in Effective Platform Engineering

Application observability is an observability practice narrowly focused on the behavior and performance of application software.

Application observability focuses narrowly on telemetry from running applications, helping engineering teams assess software health and diagnose problems. section 5.1.2

Treating it as the whole observability strategy creates a blind spot: application and infrastructure data alone can miss customer experience, cost, security, governance, and business questions. section 5.1.2

Operational blind spot

A drop in repeat users may appear in application behavior, but delayed conversion data can prevent timely action; daily GDPR reporting may also lack an automated mechanism. section 5.1.2

Figure 5.2 Observability data can be described across multiple engineering and business operations facets. Users and use cases are more than developers and operations personnel responsible for running the system. Stakeholders, security, and governance also have questions that the data can answer.

Use the observability-facets diagram to place application telemetry alongside infrastructure, stakeholder, security, governance, and other operational concerns. section 5.1.2

How Effective Platform Engineering covers it

How deep it goes

Defines the focus and limits of application telemetry but defers detailed collection and implementation patterns.

Examples

Uses conversion decline, stale reporting, cloud overruns, and GDPR reporting as surrounding observability scenarios.

What you can do after

Diagnose application problems and recognize when application telemetry alone cannot explain broader operational outcomes.

How it connects

Connects application observability with infrastructure observability, customer experience, security, governance, and business strategy.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• antipatternkind of · An antipattern is a recurring approach that appears reasonable but tends to produce undesirable or counterproductive results in a given context.
• metricmeasured by · A metric is a quantitative measure used to characterize or assess a property, condition, behavior, performance, or outcome.
• observabilitykind of · Observability is the ability to infer a system’s internal state and behavior from its externally available outputs, such as logs, metrics, and traces.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.