chore: Add Custom OpenTelemetry Exporter in for Service Metrics #1273
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.
This change adds an implementation for an OpenTelemetry exporter to send the following service metrics that are already present in the Go and Java clients:
operation_latencies
operation_count
attempt_latencies
attempt_count
gfe_latency
gfe_missing_header_count
Files added to a
metrics
folder in/google/cloud/spanner_v1/metrics
metrics_exporter.py
- The definition for the exporterconstants.py
- Constant values such as metric and label names to be used by both the exporter and eventual implementing code.Based on regular client Google Cloud Monitoring exporter found here
note: CLA not signed yet, as there's a settings issue. Will have it submitted soon.
note2: Linter runs with no issues, currently working on generating code coverage report to verify full coverage.