mirror of
https://github.com/SigNoz/signoz.git
synced 2026-10-07 02:30:42 +01:00
1643df620b
Some checks failed
build-staging / prepare (push) Has been cancelled
build-staging / js-build (push) Has been cancelled
build-staging / go-build (push) Has been cancelled
build-staging / staging (push) Has been cancelled
cacheci / tests (push) Has been cancelled
Release Drafter / update_release_draft (push) Has been cancelled
#### Description Phase 2 of #6143: semantic-convention families resolve on logs and metrics, behind the `resolve_semconv_families` flag (default off), on the storage contract of #12802. - Registry: each member carries the scope of its own rename edges, so a fan-out keeps one membership per target and an ambiguous name stays literal. - Logs and metrics families need no family code of their own. The gate applies to every signal, and `LogicalRead` merges members through each storage's `Read`. - Metric-name families union the storage names in every `metric_name` filter, and the querier reads type, temporality, and the reduced flag across the family. - Span-metrics labels: the metrics the processor emits, listed by name, also read each family member with the `resource_` prefix. Requested names are never rewritten. - Values suggestions and related values cover every spelling of the family. - `deployment.environment.name` resolves on all three signals. `db.system.name` stays off until a value-mapping reader exists. #### Additional Information - `pkg/semconv.Family` fields are now unexported, and `transition.go` is removed. #12446 reads the old API and needs an update when stacked. - A target that emits both names of a metric-name family double-counts in `sum()` during the overlap window. Reading both names is the feature. Pinned by a test. - A family of metrics labels keeps the keyless contract of a single label: no guard, no NULL group.