Area(s)
area:dns
What's missing?
OBI is currently allows to produce the dns.lookup.duration as opt-in. we started of following the otel semconv by always adding the dns.question.name attribute on the metric. But we change it to be opt-in because of unbounded cardinality issues which causes issues for users.
OBI declares its own telemetry schema that inherits from the otel registry. but if we downgrade the existing requirement level from required to opt-in that is a breaking change since users will expect that label
Describe the solution you'd like
Since this metric is still in development and dns.question.name does have boundless cardinality i would like to propose to convert it to opt-in instead of required inside the otel semconv
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Area(s)
area:dns
What's missing?
OBI is currently allows to produce the
dns.lookup.durationas opt-in. we started of following the otel semconv by always adding thedns.question.nameattribute on the metric. But we change it to be opt-in because of unbounded cardinality issues which causes issues for users.OBI declares its own telemetry schema that inherits from the otel registry. but if we downgrade the existing requirement level from
requiredtoopt-inthat is a breaking change since users will expect that labelDescribe the solution you'd like
Since this metric is still in development and
dns.question.namedoes have boundless cardinality i would like to propose to convert it toopt-ininstead ofrequiredinside the otel semconvTip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding
+1orme too, to help us triage it. Learn more here.