Avatar for the open-telemetry user
open-telemetry
opentelemetry-collector
BlogDocsChangelog

Branches performance

Pull requests

[cmd/mdatagen] Generate required fields validation for go config structs#14768
last run
2 days ago
Generate required fields validation for go config structs
3 days ago
c6192f7
jkoronaAtCisco:go_validators_mdatagen
CodSpeed Performance Gauge
+28%
[chore][pkg/exporterhelper] fix test naming and referenced attributes#14767
last run
3 days ago
fix TestComponentInstrumentation Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
3 days ago
8ebc2bd
florianl:xexporterhelper-bug
CodSpeed Performance Gauge
0%
changelog: add entry for v1.10.0 proto upgrade
3 days ago
b5f84b6
felixge:felixge/otlp-v1.10.0
CodSpeed Performance Gauge
-1%
[cmd/mdatagen] Rename per-metric config types to include Metric infix Rename generated types for per-metric reaggregation config to make the category explicit and avoid future name collisions: - `{MetricName}Config` -> `{MetricName}MetricConfig` - `{MetricName}AttributeKey` -> `{MetricName}MetricAttributeKey` For example, for the `system.cpu.frequency` metric: - `SystemCPUFrequencyConfig` -> `SystemCPUFrequencyMetricConfig` - `SystemCPUFrequencyAttributeKey` -> `SystemCPUFrequencyMetricAttributeKey` Without the infix, `{MetricName}Config` is ambiguous — it could be confused with any other `Config` struct in the codebase. Adding `Metric` makes the category explicit and consistent with the surrounding generated types (`MetricsConfig`, `MetricsBuilderConfig`, etc.). Also fix the `slices` import to only be emitted when there are actually required attributes (which produce `slices.Contains` calls), rather than whenever any aggregatable attributes exist.
3 days ago
5698c74
dmitryax:add-metric-config-suffix
CodSpeed Performance Gauge
-3%
© 2026 CodSpeed Technology
Home Terms Privacy Docs