Capabilities being explored
The Observability Platform discovery is exploring what a future offering should support. The areas below are discussion topics, not a committed service catalogue, selected product, or delivery roadmap.
For the existing service, see the current architecture and user guide.
Accessing and connecting telemetry
We want to understand how teams collect and access logs, metrics, and traces, and where it is difficult to connect information across applications and infrastructure. Discovery will consider existing data sources and data-handling constraints rather than assume all data should be moved into a new service.
Dashboards and service health
We want to understand which views help teams assess service health, how dashboards are maintained and shared, and where common approaches could help without losing application-specific context.
Alerting and investigation
We want to understand how teams identify actionable signals, manage alert noise, and investigate incidents. This includes the role of existing notification and incident management workflows and any gaps between receiving an alert and finding its cause.
Integration and onboarding
We want to understand what would make a future offering practical to adopt: integration with existing environments, identity and access requirements, configuration workflows, documentation, and the effort required from teams.
This is not an onboarding process for a new live service. Existing users should continue to refer to the current user guide.
Ownership and support needs
We want to understand which responsibilities should remain with application teams and where shared capabilities, guidance, or support could help. Discovery does not establish a support model, service level, or ownership arrangement for a future platform.
Shape these areas
The scope should follow from teams’ needs and experiences. Share missing capabilities, constraints, and examples of what works today through #ask-observability-platform.