How coroot/coroot-aws-agent works
Component Interactions
• Discovery flows from AWS Services to respective Discovery components
• Metric collection flows from AWS Services to respective Collectors
• Enhanced monitoring flows for RDS
• Log collection flows for RDS
• Metric export flow to Prometheus
Detailed Component Breakdown
For each major component, create a sub-section showing:
RDS Package:
collector.go ─→ Enhanced Monitoring
• → Log Collection
discovery.go ─→ Auto-discovery
enhanced.go ─→ Enhanced metrics processing
logs.go ─→ Log processing
ElastiCache Package:
collector.go ─→ Metrics Collection
discovery.go ─→ Auto-discovery
Additional Elements
Supporting elements:
• Configuration flow from flags package
• Utility functions from utils package
• Docker container boundary (since Dockerfile is present)
• GitHub Actions workflow for CI/CD (indicated by docker-publish.yml)
Technical Details
Annotations showing:
• Supported AWS services (RDS PostgreSQL/MySQL, ElastiCache Redis/Memcached)
• Metric types collected (OS metrics, database metrics, log-based metrics)
• Auto-discovery capabilities
• Enhanced Monitoring integration
Design Principles to Highlight
Emphasize:
• Modular architecture (separate packages for different services)
• Service discovery mechanism
• Metric collection abstraction
• Prometheus export capability
Remember to indicate that this is a containerized application that can be deployed anywhere with AWS access, and show the configuration options available through the flags package.
This design should effectively communicate both the overall system architecture and the specific components that make this AWS metrics exporter function.