-
Notifications
You must be signed in to change notification settings - Fork 4k
changefeedccl: add static labels to changefeed metrics #156901
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
base: master
Are you sure you want to change the base?
Conversation
|
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
ccc8ce5 to
8713506
Compare
log-head
left a comment
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.
Looks good! Wondering if you think we should add a unit test for using these through the /metrics endpoint? I did cursory manual testing on this branch and the static labeled metrics show up.
Metrics change detectedThis PR adds or updates one or more CRDB metrics. If you want these metrics to be exported by CRDB Cloud clusters to Internal CRL Datadog and/or included in the customer metric export integration (Essential metrics for standard deployment, and Essential metrics for advanced deployment), refer to this Installation and Usage guide of a CLI tool that syncs the metric mappings in managed-service. Run this CLI tool after your CRDB PR is merged.
Note: Your metric will appear in Internal CRL Datadog only after the managed-service PR merges and the new OTel configuration rolls out to at least one cluster running a CRDB build that includes this metric. Docs: cockroach-metric-sync Questions: reach out to @obs-india-prs |
8713506 to
25158e2
Compare
| PTSManage: b.Histogram(histogramOptsFor("changefeed.stage.pts.manage.latency", "Latency of the changefeed stage: Time spent successfully managing protected timestamp records on highwater advance, including time spent creating new protected timestamps when needed")), | ||
| PTSManageError: b.Histogram(histogramOptsFor("changefeed.stage.pts.manage_error.latency", "Latency of the changefeed stage: Time spent managing protected timestamp when we eventually error")), | ||
| PTSCreate: b.Histogram(histogramOptsFor("changefeed.stage.pts.create.latency", "Latency of the changefeed stage: Time spent creating protected timestamp records on changefeed creation")), | ||
| CheckpointJobProgress: b.Histogram(stageOpts("checkpoint_job_progress", "Latency of the changefeed stage: checkpointing job progress")), |
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.
i get the appeal but i actually dont think we should do it like this. the ability to grep the codebase for the literal metric name should not be underestimated. can you alter your approach to maintain that feature pls
25158e2 to
5df1d6e
Compare
5df1d6e to
817d91c
Compare
Potential Bug(s) DetectedThe three-stage Claude Code analysis has identified potential bug(s) in this PR that may warrant investigation. Next Steps: Note: When viewing the workflow output, scroll to the bottom to find the Final Analysis Summary. After you review the findings, please tag the issue as follows:
|
817d91c to
ce1f3d2
Compare
This commit adds static labels to changefeed stage and emitted metrics metrics. Resolves: cockroachdb#156290 Release note: None
ce1f3d2 to
3bd384c
Compare
|
AI did find a real issue but it was also caught by a failed test in CI. |
This commit adds static labels to changefeed stage and emitted metrics
metrics.
Resolves: #156290
Release note: None