feat(telemetry): introduce opentelemetry metrics to cody #CODY-5585 #7647
Conversation
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
- push seems to be working - but not seeing metric on dashboards
valerybugakov
approved these changes
Apr 8, 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.
Introduces OpenTelemetry's metrics support to cody client. This allows cody client to send real-time metrics (currently every minute) for observability, monitoring. The metrics can be queried with prometheus or GCP's metric explorer. For example:
No additional configuration is required. New metrics will automatically appear in GCP's metric explorer.
In addition, with the version field (attached to the meter), the metrics can be used for release gating before rolling out to all populations.
Test plan