Infrastructure

Infrastructure Catalog provides a live map of your production environment — clusters, node pools, namespaces, and more — giving engineers deep visibility into the systems behind every service and alert.

Infrastructure context is critical during investigations, helping identify affected components, related assets, and potential root causes.

​

⚙️ Ways to Add Infrastructure

Infrastructure resources can be added in two ways:

​

✅ 1. Auto-Sync from Cloud & Kubernetes Integrations

DrDroid automatically discovers and syncs infrastructure metadata from:

​

Cloud Providers

• AWS (EKS), GCP (GKE), Azure
• VM instances, node groups, autoscaling configs

​

Kubernetes Clusters

• Namespaces, deployments, statefulsets, services
• Ingresses, network policies, autoscalers, and more

🧠 Once integrations are active, infrastructure is auto-populated and continuously synced — no setup required.

​

📝 2. Manual Addition via UI

For custom environments or fine-tuned control, users can manually add infrastructure components.

​

Steps:

1. Navigate to Context → Catalog → Infrastructure
2. Click ”+ Add Resource”
3. Provide details:
   • Resource Type (e.g., cluster, namespace, deployment)
   • Name (e.g., eks-prod-cluster-1)
   • Region / Zone (if applicable)
   • Linked Services (optional)
   • Tags (e.g., prod, critical, shared)
4. Click Save

🔗 These resources can then be referenced by alerts, services, or during task execution.

​

🧩 What Gets Cataloged?

Depending on the integration, DrDroid may capture:

​

🔄 Keeping Infra Up to Date

• Auto-synced infra is kept fresh through connected integrations.
• Manually added items can be edited, updated, or removed anytime.