Link Catalog with Synthetic & Third Party Monitors
The Monitoring section inside Catalog entities allows teams to connect observability tools directly to services, systems, and operational components.
By linking monitors to catalog entities, teams gain centralized visibility into service health, uptime, and third-party dependencies.
How To: Configuring Monitor Links in the Catalog Monitoring Tab
Why monitor associations matter
Attaching monitors directly to catalog entities helps operational teams:
- Understand service health in one centralized location
- Connect incidents to affected monitored systems
- Improve operational visibility during outages
- Track external dependency reliability
- Simplify troubleshooting and ownership resolution
This creates stronger alignment between observability and operational workflows.
Supported monitoring integrations
Catalog entities can be associated with different monitoring sources, including:
- Synthetic Monitors — Simulate user journeys and endpoint availability
- Third Party Monitors — External provider integrations and dependency health
- Endpoint Monitoring — API and service availability checks
- Operational Health Signals — Linked telemetry and observability systems
These integrations help teams proactively identify issues before they impact users.
Linking monitoring systems to catalog entities improves incident triage, operational awareness, and service dependency tracking.
Managing monitor links
From the Monitoring tab, teams can:
- Add or remove monitor associations
- Configure monitor types
- Associate external monitoring providers
- Update linked synthetic monitors
- Maintain service-level observability mappings
This ensures catalog entities remain aligned with current operational monitoring workflows.
Synthetic and third-party visibility
Synthetic monitors help validate service reliability through simulated checks and workflows, while third-party integrations provide visibility into external platforms and dependencies.
Together, these integrations create a more complete operational view across internal systems and external services.
Best practices
- Associate monitors with all production-critical services
- Keep monitoring links updated as systems evolve
- Use consistent naming conventions for monitors
- Review third-party dependencies regularly
- Remove outdated or deprecated monitoring associations