Services represent core application components such as APIs, microservices, or backend jobs. You can build and manage a complete Service Catalog โ€” automatically or manually โ€” to enrich your alert investigations, runbooks, and debugging flows.

We support both automatic discovery and manual service creation.


โœ… 1. Auto-Mapping via Integrations

When you connect your APM, CI/CD, or Kubernetes integrations (e.g., Datadog, New Relic, GKE, EKS), DrDroid will:

  • Detect running services based on traces, deployments, or job definitions
  • Populate the catalog with service names, metadata, and linked resources
  • Continuously sync to stay up to date

๐Ÿ“ No manual effort is required โ€” detected services appear in your catalog automatically.


๐Ÿ“ 2. Manual Addition via UI

You can also create services manually for full control or to supplement whatโ€™s auto-detected.

Steps:

  1. Go to Context โ†’ Catalog โ†’ Services
  2. Click โ€+ Add Serviceโ€
  3. Fill out the service details:
    • Service Name (e.g., payments-api)
    • Team / Owner (optional, for tagging and ownership clarity)
    • Environment (e.g., prod, staging)
    • Tags (e.g., billing, critical)
    • Linked Integrations (optional)
  4. Click Save

๐Ÿ”— You can link the service later to alerts, tasks, or runbooks for enriched context.


๐Ÿง  Why Add Services?

  • Connect alerts to relevant systems automatically
  • Simplify incident triage with ownership visibility
  • Enable AI-assisted debugging with more context
  • Tag services for better filtering and grouping