[cluster telemetry] internal service types#7599
Merged
Conversation
9b662d4 to
bcf2900
Compare
2 tasks
timvisee
reviewed
Dec 3, 2025
Comment on lines
+13
to
+21
| message GetPeerTelemetryResponse { | ||
| reserved 1; // id | ||
| reserved 2; // app | ||
| map<string, CollectionTelemetry> collections = 3; // Mapping from collection name to its telemetry | ||
| ClusterTelemetry cluster = 4; // Telemetry about the cluster and peers | ||
| reserved 5; // requests | ||
| reserved 6; // memory | ||
| reserved 7; // hardware | ||
| } |
Member
There was a problem hiding this comment.
So this basically follows the same structure as our existing telemetry, but it is very limited.
Is there a strong argument for doing it this way, versus implementing a whole new kind of telemetry with it's own fields?
Contributor
Author
There was a problem hiding this comment.
Yes, and it is made to replicate it closely.
We already have the information we need from existing telemetry, so we can reuse the collectors we already have for internal service.
timvisee
approved these changes
Dec 4, 2025
timvisee
pushed a commit
that referenced
this pull request
Dec 18, 2025
* stripped down grpc types for peer telemetry * return err instead of panic * use correct definitions * improve types
This file contains hidden or 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
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.
As a first step towards aggregating telemetry from all peers, we need to be able to communicate telemetry with other peers. This can only be done through the internal service.
This PR adds internal service types for mapping current telemetry into internal service. For now, we include only info about the peer, resharding, and shard transfers.