Closed yzhaoa closed 1 year ago
Hi @yzhaoa,
custom.googleapis.com
and it should fix your issue. I see that you have created the Metric Exporter with default config - so you will probably need to use setPrefix to change the default workload.googleapis.com
.
You can read the comments in #155 - which cites the exact same issue that you mentioned.
Based on this comment from this issue - workload.googleapis.com
is allowed to be used, despite the deprecation.
Hi @yzhaoa, were you able to resolve your issue with the provided information ?
Closing this issue. Feel free to re-open in case the underlying issue is still unresolved.
Based on https://cloud.google.com/monitoring/custom-metrics#identifier, the only allowable metric prefixes are custom.googleapis.com/, external.googleapis.com/user, and external.googleapis.com/prometheus.
Using the current default of workload.googleapis.com, I run into the following error:
Using the following OpenTelemetry manual instrumentation configuration plus manual gRPC server instrumentation using GrpcTelemetry:
I see the following error when running under GCP:
Under debugging, I captured the offending CreateMetricDescriptorRequest:
For reference, the meter is defined at: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/3611f11e3966f2b87da262dc8536e92a5c2747a4/instrumentation-api-semconv/src/main/java/io/opentelemetry/instrumentation/api/instrumenter/rpc/RpcClientMetrics.java#L41