How prometheus-community/yet-another-cloudwatch-exporter works
Main Components
a. Core Components:
• AWS CloudWatch (External Service)
• YACE Exporter Core
• Prometheus Server (External Service)
• AWS IAM/STS (Authentication Layer)
b. Internal YACE Components:
• Config Management (/pkg/config)
• Client Layer (/pkg/clients)
• Job Management (/pkg/job)
• Metrics Model (/pkg/model)
• Prometheus Utilities (/pkg/promutil)
Component Relationships and Data Flow
[AWS CloudWatch] <---> [YACE Exporter Core] <---> [Prometheus Server]
• v
[AWS IAM/STS] <---> [Authentication Layer]
Detailed Component Breakdown
• YACE Exporter |
• Config Management |
• Client Layer |
• Job Management |
• Metrics Model |
• Prometheus Utils |
Key Interactions to Highlight
a. Discovery Flow:
[Config] -> [Job Management] -> [AWS Clients] -> [CloudWatch API]
b. Metrics Collection Flow:
[CloudWatch] -> [YACE Clients] -> [Metrics Model] -> [Prometheus Format]
Technical Details
• Scraping intervals
• Concurrency limits
• AWS SDK integration points
• Metric data formats
• Resource discovery mechanisms
Implementation Notes
Emphasize:
• Decoupled scraping architecture
• Background metric collection
• Resource tagging system
• CloudWatch API optimization
• Cross-account role assumption