-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat: metrics schema version #12732
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
feat: metrics schema version #12732
Conversation
5025e2a
to
8fdc9e8
Compare
Test Results - Alternative Providers987 tests 589 ✅ 29m 44s ⏱️ Results for commit ea2ffc8. ♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 21m 16s ⏱️ For more details on these failures, see this check. Results for commit ea2ffc8. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files 2 suites 1h 42m 38s ⏱️ For more details on these failures, see this check. Results for commit ea2ffc8. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, and in my opinion you should just define this on the base Metric
class from the beginning. However, I'll totally leave this up to you! Thanks for continuously improving the metrics framework! 💯
… and LabeledCounter
c475ccf
to
ea2ffc8
Compare
FYI: The three failing tests are unrelated / are also failing on |
Motivation
This PR introduces explicit schema versioning for metrics definitions. The goal is to make telemetry changes safer and more maintainable:
For now:.
However, having the
schema_version
available in Tinybird helps with:status
of a request, with possible values like "success" and "error". Later, the counter is updated: a new label label_2 is introduced to hold the status instead:A more structured approach would require:
Changes