-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add snapshot test of prometheus metrics #10911
Labels
Comments
gibson042
added a commit
that referenced
this issue
Feb 6, 2025
gibson042
added a commit
that referenced
this issue
Feb 6, 2025
gibson042
added a commit
that referenced
this issue
Feb 6, 2025
This was referenced Feb 7, 2025
gibson042
added a commit
that referenced
this issue
Feb 7, 2025
mergify bot
added a commit
that referenced
this issue
Feb 9, 2025
Extends #10941 Fixes #10911 ## Description Extracts a testable `launchChain` unit in packages/cosmic-swingset/src/chain-main.js, and uses that for an ava snapshot test of localhost:${OTEL_EXPORTER_PROMETHEUS_PORT}/metrics. Includes incidental fixes and utility additions along the way (and therefore best reviewed by commit). ### Security Considerations None known. ### Scaling Considerations n/a ### Documentation Considerations n/a ### Testing Considerations Just the usual `--update-snapshots` when things change. ### Upgrade Considerations n/a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
We should understand the impact of making changes to our prometheus metrics. While there is various ways to confuse consumers of these, the most obvious one is a change in which metrics are reported. Another is possibly a change in the type or characteristic of the metric
Description of the Design
A snapshot style test, at worse in a3p-integration (but preferably in an ava based required test, like in the cosmic-swingset package), that queries the metrics Prometheus endpoint and snapshots at least the set of metrics exported, and if possible metadata about the characteristics of these metrics.
Security Considerations
None
Scaling Considerations
None
Test Plan
This is a test
Upgrade Considerations
None
The text was updated successfully, but these errors were encountered: