Skip to content

Conversation

@TheOneFromNorway
Copy link
Contributor

@TheOneFromNorway TheOneFromNorway commented Dec 4, 2025

  • This forms a basic setup where exporting any metric via prometheus also exports this metric to cloudwatch
    • Simplifies future metric exports and expanding on our monitoring structure
  • Metrics from sidekiq and puma have been introduced in this PR as areas where we are currently more critically in need of insights

JIRA Ticket MAV-2918

@TheOneFromNorway TheOneFromNorway force-pushed the prometheus_exports_to_cloudwatch_metrics branch 3 times, most recently from 7bd0ded to 739752e Compare December 19, 2025 21:50
@TheOneFromNorway TheOneFromNorway marked this pull request as ready for review December 19, 2025 21:55
@TheOneFromNorway TheOneFromNorway requested review from a team as code owners December 19, 2025 21:55
- Working setup but parameters need tuning/changing
- This forms a basic setup where exporting any metric via prometheus
  also exports this metric to cloudwatch
  - Simplifies future metric exports
- CloudWatch exporting should not be considered part of the main
  application, so run it as a agent in sidecar
- Add labels to allow identifying which container/service the metrics
  originate from
- Conditional logic determines which containers are spun up
- Environment variables to establish which metrics to export in
  application
@TheOneFromNorway TheOneFromNorway force-pushed the prometheus_exports_to_cloudwatch_metrics branch from 739752e to d42479c Compare December 19, 2025 21:59
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants