Details
-
Bug
-
Status: Open
-
P2
-
Resolution: Unresolved
-
2.34.0
-
None
Description
IO request count metrics calculated incorrectly for GCP Spanner
Resource ID is formulated incorrectly
Spanner Table:
//spanner.googleapis.com/projects/{projectId}/topics/{databaseId}/tables/{tableId}
should be
//spanner.googleapis.com/projects/{projectId}/instances/{instanceId}/databases/{databaseId}/tables/{tableId}
and is populated incorrectly – instance ID is used in place of tableID
Spanner SQL Query:
//spanner.googleapis.com/projects/{projectId}/queries/{queryName}
should be
//spanner.googleapis.com/projects/{projectId}/instances/{instanceId}/queries/{queryName}
and queryName is nullable which cause issued downstream
this is not actually populated at all - queries are logged as reads on an instance.
Attachments
Issue Links
- links to