[receiver/chrony] Enable re-aggregation feature#1
Closed
lazureykis wants to merge 1 commit into
Closed
Conversation
lazureykis
force-pushed
the
chrony-enable-reaggregation
branch
from
8cdd259 to
fc5f371
Compare
Set reaggregation_enabled: true and requirement_level: recommended for the leap.status attribute, allowing users to reduce metric cardinality by dropping the attribute and aggregating datapoints. Fixes open-telemetry#46350 Assisted-by: Claude Opus 4.6
lazureykis
force-pushed
the
chrony-enable-reaggregation
branch
from
fc5f371 to
7bd5d64
Compare
lazureykis
pushed a commit
that referenced
this pull request
Apr 15, 2026
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add support timeout setting for telemetrygen <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#47203 #### Testing Sending traces to a collector that has an artificial delay of `10s` before answering ``` ❯ go run . traces --traces 1 --timeout 5s --otlp-insecure 2026-04-01T17:29:31.673+0300 INFO channelz/trace.go:200 [core] [Channel #1] Channel Connectivity change to READY {"grpc_log": true} 2026/04/01 17:29:34 traces export: context deadline exceeded: rpc error: code = DeadlineExceeded desc = context deadline exceeded 2026-04-01T17:29:34.980+0300 INFO channelz/trace.go:200 [core] [Channel #1] Channel Connectivity change to SHUTDOWN {"grpc_log": true} ``` ``` ❯ go run . traces --traces 1 --timeout 15s --otlp-insecure 2026-04-01T17:30:42.046+0300 INFO channelz/trace.go:200 [core] [Channel #1] Channel Connectivity change to READY {"grpc_log": true} 2026-04-01T17:30:52.052+0300 INFO channelz/trace.go:200 [core] [Channel #1] Channel Connectivity change to SHUTDOWN {"grpc_log": true} ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Enables dynamic metric reaggregation in the Chrony receiver. Collector configuration files can now define a set of attributes per metric to aggregate data by. This can be done for any metric attribute at a requirement level of
recommendedor below.For more information about how reaggregation works, see open-telemetry/opentelemetry-collector#14281.
Changes:
reaggregation_enabled: trueinmetadata.yamlleap.statusattribute torequirement_level: recommendedgo generate ./...to regenerate all derived filesLink to tracking issue
Fixes open-telemetry#46350
Part of open-telemetry#45396
Testing
go test -race ./...inreceiver/chronyreceiver/— all 27 tests pass (includingreaggregate_set)go vet ./...— cleanmake chlog-validate— validDocumentation
No documentation changes needed. The generated
documentation.mdis updated automatically bygo generate.