-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Metrics and Tracing #1210
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
enocom
added
priority: p0
Highest priority. Critical issue. P0 implies highest priority.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
labels
Mar 15, 2023
enocom
added
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
priority: p2
Moderately-important priority. Fix may not be included in next release.
and removed
priority: p0
Highest priority. Critical issue. P0 implies highest priority.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
labels
Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Feature Description
We should use the Go Connector as the reference implementation and provide the same metrics / traces. We should also use Open Telemetry.
See https://github.com/GoogleCloudPlatform/cloud-sql-go-connector#enabling-metrics-and-tracing
The text was updated successfully, but these errors were encountered: