grpc/grpc-java

Cardinality of grpc_target attribute for grpc.client.* metrics is too large

Open

#12,322 创建于 2025年8月28日

在 GitHub 查看
 (9 评论) (0 反应) (0 负责人)Java (11,124 star) (3,742 fork)batch import
enhancementhelp wanted

描述

What version of gRPC-Java are you using?

1.71.0

What is your environment?

OS: Linux JDK: 21

What did you expect to see?

No warnings when enabling default OpenTelemetry metrics.

What did you see instead?

WARNING: Instrument grpc.client.attempt.started has exceeded the maximum allowed cardinality (1999).
WARNING: Instrument grpc.client.attempt.rcvd_total_compressed_message_size has exceeded the maximum allowed cardinality (1999).
WARNING: Instrument grpc.client.attempt.sent_total_compressed_message_size has exceeded the maximum allowed cardinality (1999).
WARNING: Instrument grpc.client.call.duration has exceeded the maximum allowed cardinality (1999).
WARNING: Instrument grpc.client.attempt.duration has exceeded the maximum allowed cardinality (1999).

This is caused by the grpc_target attribute having a very large cardinality.

I see that this attribute is listed for these metrics at https://github.com/grpc/proposal/blob/master/A66-otel-stats.md. However, for very large deployments this can be problematic. Is there a way to turn this attribute off?

Steps to reproduce the bug

Have a client which connects to 2000+ servers (either at once or over time).

贡献者指南

技术栈
javaopentelemetry
领域
backendobservability
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
gRPC Java basicsOpenTelemetry instrumentationJava programming
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Examine the gRPC Java implementation of OpenTelemetry metrics, specifically the grpc target attribute in client metrics. Look for where the attribute is set (likely in the client call instrumentation) and consider adding a configuration option to disable it. Review the proposal A66 otel stats.md for context on the attribute's purpose. Also check if there are existing configuration flags for cardinality control in the gRPC Java codebase.