Export reporting API totals to Prometheus (hourly job)#6153
Draft
MartinVanIJcken wants to merge 1 commit intonextfrom
Draft
Export reporting API totals to Prometheus (hourly job)#6153MartinVanIJcken wants to merge 1 commit intonextfrom
MartinVanIJcken wants to merge 1 commit intonextfrom
Conversation
MartinVanIJcken
force-pushed
the
track-reporting-totals-in-prometheus
branch
from
a282dff to
f04696a
Compare
Same pattern as existing Prometheus exports: Puma uses EXPORT_PUMA_METRICS and PrometheusExporter::Instrumentation::Puma (config/puma.rb); Sidekiq uses EXPORT_SIDEKIQ_METRICS and PrometheusExporter::Instrumentation for process, queues and stats (config/initializers/sidekiq.rb). Both push to the same exporter (bin/prometheus_exporter on port 9394) via PrometheusExporter::Client.default. This job adds reporting API totals as gauges, gated by EXPORT_REPORTING_METRICS, using the same client to register and observe. Intended for the ops service where the exporter runs alongside Sidekiq. Schedule in config/sidekiq.yml hourly; spec covers guards and observations.
MartinVanIJcken
force-pushed
the
track-reporting-totals-in-prometheus
branch
from
f04696a to
680a300
Compare
Contributor
|
Following further discussions, we think it makes more sense to use the CloudWatch API directly to export application-level metrics like these. See #6498 for an example of this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Same pattern as existing Prometheus exports: Puma uses EXPORT_PUMA_METRICS and PrometheusExporter::Instrumentation::Puma (config/puma.rb); Sidekiq uses EXPORT_SIDEKIQ_METRICS and PrometheusExporter::Instrumentation for process, queues and stats (config/initializers/sidekiq.rb). Both push to the same exporter via PrometheusExporter::Client.default.
This job adds reporting API totals as gauges, controlled by EXPORT_REPORTING_METRICS, using the same client to register and observe. Intended for the ops service where the exporter runs alongside Sidekiq. Schedule in config/sidekiq.yml hourly; spec covers guards and observations.
Screenshots
Pre-release tasks
Post-release tasks