Understand Your System

Scenario

A new engineer joins the team and needs to understand how services are connected, what's running in production, and how the infrastructure is configured. Or an experienced engineer needs to quickly understand a part of the system they don't usually work with.

How OpsWorker Helps

Interactive Cluster Exploration

Use AI Chat as a live, interactive documentation tool:

You: What services are running in namespace production?

OpsWorker: There are 12 services in the production namespace:
- api-gateway (3 replicas, exposed via ingress)
- user-service (2 replicas)
- payment-processor (3 replicas)
- ...

You: What services depend on database-service?

OpsWorker: Based on the service topology:
- user-service connects to database-service on port 5432
- payment-processor connects to database-service on port 5432
- analytics-worker connects to database-service on port 5432

You: Describe the deployment configuration for api-gateway

OpsWorker: Deployment api-gateway in namespace production:
- Replicas: 3 (managed by HPA, min 2, max 10)
- Image: api-gateway:v2.4.1
- Resource limits: 500m CPU, 512Mi memory
- Environment variables: 12 configured
- Mounted configmaps: api-config
- Health checks: HTTP readiness on /health, liveness on /ping

Investigation-Based Learning

Past investigations provide a learning resource:

• Review how issues were diagnosed and resolved
• Understand common failure patterns for your infrastructure
• See how services interact under failure conditions

Topology Visualization

Investigation detail pages show topology maps of affected resources, making service dependencies visible.

Outcome

• Faster onboarding — New team members explore the cluster through conversation, not documentation that may be outdated
• Always current — AI Chat queries live cluster data, not stale docs
• Reduced knowledge silos — Anyone can explore any part of the system
• No kubectl expertise required — Ask natural language questions instead of memorizing kubectl syntax