Monitoring

Discovery

Discovery helps teams identify URLs and endpoints that should become monitors, reducing the chance that new product surfaces ship unmonitored.

Audience: Engineering teams, founders, platform teams

How discovery helps

  • Scans application URLs and known endpoint sources.
  • Suggests monitor candidates from discovered routes.
  • Helps identify new endpoints after product changes.
  • Reduces manual monitor setup work for growing applications.

Review process

  • Review discovered endpoints before creating monitors.
  • Prioritize customer-facing and critical workflow endpoints.
  • Avoid creating monitors for noisy, private, or low-value URLs.
  • Add keyword or expected status validation after creating an HTTP monitor.

Troubleshooting

  • If discovery misses routes, confirm the app exposes links, sitemap entries, or OpenAPI data.
  • If discovery finds too much, focus on pages and APIs that represent important user journeys.
  • Use service ownership to organize discovered monitors after creation.

Related documentation