structlogging: move hot ranges log over to the OPS channel #143513
+79
−79
Conversation
This file contains 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
angles-n-daemons
requested review from
kyle-a-wong,
arjunmahishi,
aa-joshi and
Abhinav1299
and removed request for
a team
![blathers[crl]](https://avatars.githubusercontent.com/in/59700?s=40&u=95b789b1d594ac6b74f377aa7555d8d98d63240d&v=4){kind=avatar}
|
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. |
|
This change is |
As title states, currently hot range logs are emitted on the TELEMETRY channel - which is generally unused and unavailable to cloud customers. By moving it to the OPS channel, we can better instruct users to find it - as well as increase the general availability on cloud deployments. Fixes: cockroachdb#143512 Epic: CRDB-43150 Release note (ops change): Move hot range logs to the OPS channel.
angles-n-daemons
force-pushed
the
hot-range-logs-to-ops
branch
from
b4a6ce3 to
a631298
Compare
alyshanjahani-crl
approved these changes
Mar 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
structlogging: move hot ranges log over to the OPS channel
As title states, currently hot range logs are emitted on the TELEMETRY channel - which is generally unused and unavailable to cloud customers. By moving it to the OPS channel, we can better instruct users to find it - as well as increase the general availability on cloud deployments.
Fixes: #143512
Epic: CRDB-43150
Release note (ops change): Move hot range logs to the OPS channel.