docs: add usage guidance for downstream_sink_latency metric #19796
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.
Relates to cockroachdb/cockroach#148417
This PR adds documentation for the changefeed.stage.downstream_sink_latency metric.
The new doc explains:
What the metric measures
When to worry about high values
Where to monitor it (Admin UI, Prometheus)
Suggested alert threshold
Possible causes and mitigations
This metric is mentioned in cockroachdb/cockroach#148417 as needing clarification.
Let me know if you'd prefer this as a user doc or if the metric should be improved instead
@rharding6373