← ClaudeAtlas

aio-grafana-diagramlisted

Create Grafana diagrams for system visualization — analyzes codebase to auto-generate Mermaid diagrams with metric binding. For standalone Mermaid diagrams use aio-mermaid instead.
aiocean/claude-plugins · ★ 3 · AI & Automation · score 65
Install: claude install-skill aiocean/claude-plugins
# Grafana Dashboard Diagram Generator ## Environment - grafana-cli: !`which grafana-cli 2>/dev/null || echo "NOT INSTALLED"` ## Objective Workflow ### Phase 1: DISCOVER — Analyze Codebase Architecture Scan the project to identify system components: 1. **Services**: Find service entry points, main files, Dockerfiles, docker-compose services 2. **APIs**: Identify HTTP routes, gRPC definitions, GraphQL schemas 3. **Data flows**: Trace database connections, message queues, cache layers, external API calls 4. **Infrastructure**: Load balancers, CDNs, monitoring endpoints from config/infra files ```bash # Example discovery commands ls docker-compose*.yml Dockerfile* k8s/ infra/ 2>/dev/null # Look for service definitions, route handlers, DB connection strings ``` Output a component inventory: `[service_name, type, connections[], metrics_available[]]` ### Phase 2: GENERATE — Create Mermaid Diagram Code Based on discovered components, generate Mermaid syntax: 1. Choose diagram type: `graph LR` (service flow), `graph TB` (layered arch), `sequenceDiagram` (request flow) 2. Create nodes with meaningful IDs matching metric naming conventions (underscores, no special chars) 3. Use subgraphs to group related services (Frontend, Backend, Data, Infrastructure) 4. Add edge labels for protocol/relationship types (HTTP, gRPC, TCP, pub/sub) 5. Keep to 10-15 nodes max for readability ### Phase 3: BIND — Map Metrics to Diagram Nodes For each node, identify and bind a relevant metric: 1