Definition: An Observability Application Component is an application component that implements capabilities to instrument, expose, collect, process, correlate, store, and provide access to application telemetry (e.g. metrics, logs, traces, and events) so that the runtime behaviour, performance, health, and reliability of digital public service applications can be assessed and troubleshot. It enables consumers (operations teams, support services, automated management components) to obtain actionable insights by analysing externally observable signals produced by applications, without requiring direct access to internal application state. This component typically provides ingestion endpoints or collectors, processing and correlation logic, storage/indexing, and query/export interfaces to support interoperable consumption of application-level diagnostics and telemetry. Source: OpenTelemetry Concepts Source reference: https://opentelemetry.io/docs/concepts/observability-primer/ Last modification: 2026-01-28 Identifier: http://data.europa.eu/dr8/ObservabilityApplicationComponent LOST view: Technical view – Infrastructure EIRA concept: eira:ArchitectureBuildingBlock Additional identifier: http://data.europa.eu/dr8/ObservabilityApplicationComponent ABB name: eira:ObservabilityApplicationComponent Example: An example is an observability component deployed for a digital public service that collects distributed traces, application logs, and runtime metrics, correlates them per request or transaction, and exposes them through query/export APIs so that operational teams can diagnose incidents (e.g. increased latency and error rates) and optimise application behaviour. Additional information: In EIRA, the Observability Application Component represents the logical application building block that realises the Observability Application Service (capability-oriented). It remains implementation-agnostic (it does not prescribe a vendor/tool), but it is the architectural placeholder for the application-level mechanisms that handle telemetry signals end-to-end (ingest → process/correlate → store → provide access/export) EIF Layer: TechnicalInfrastructure Interoperability Dimension: Structural IoP