When an application becomes slow or unavailable, a team needs evidence of what changed. Monitoring tools collect measurements, record events and raise alerts; dashboards help people interpret that information. This collection includes collectors, databases, visual interfaces and related diagnostic tools. They may work together, so choose the missing part of your monitoring setup rather than treating every entry as a competing complete system.

Start with the question your platform needs to answer: service health, a failed request, unexpected resource consumption or a dependency problem. Metrics, logs and traces offer different views; a collection pipeline must also account for retention, access and operating cost.

Read the observability comparison before choosing a tool. This collection includes historical records; their presence does not establish current support.

Tools in the collection

Plan the collection layer

Identify which team owns instrumentation, telemetry collection and the backend. Follow the OpenTelemetry Collector guide to review the boundary between those responsibilities.

Sources & further reading

  1. OpenTelemetry observability primer

Spotted something that needs another look?

Help improve this page →