Version: 5.1

Observe

Observability is how you understand an integration's runtime behavior, using metrics, logs, and traces. WSO2 Integrator emits all three, and you choose where they go.

Two distinct activities sit under this heading, and it is worth keeping them apart:

Monitoring answers "is it behaving as expected?" It watches known indicators and alerts when they fall outside expected ranges. Useful for problems you anticipated.
Diagnosis answers "why is it behaving this way?" It uses logs, metrics, and traces to explain what is actually happening. Useful for problems you did not anticipate.

Observability follows your deployment

Like managing integrations, how you observe them depends on where they run:

Deployed to WSO2 Cloud: observability is built in, with nothing to set up. See Observe on WSO2 Cloud.
Running on your own infrastructure: the Integration Control Plane surfaces health, metrics, and logs, and you can send the same telemetry to the open-source or commercial tools below.

The three pillars of observability

Pillar	Purpose	Key Metrics	Built-in Support
Metrics	Quantitative measurements of system behavior	Request counts, latency, error rates, throughput	Prometheus-compatible endpoint
Logging	Structured event records for debugging and auditing	Log entries with context, error details, request tracing	Ballerina `log` module with configurable levels
Distributed Tracing	End-to-end request flow across services	Span duration, service dependencies, bottlenecks	OpenTelemetry-based tracing