open-telemetry/opentelemetry-collector

opentelemetry-collector

Performance History

Latest Results

[mdatagen] Enable configurable attributes for metrics (#14281) Reopens [13900](https://github.com/open-telemetry/opentelemetry-collector/pull/13900) #### Description Modified `cmd/mdatagen` to allow for two new fields in the configuration yaml of metrics. These new configuration options will allow for a user to enable or disable attributes (i.e. reduce dimensionality of metrics being generated) from their collector configuration. The modified `MetricsBuilder` generated by `mdatagen` does not record disabled attributes and automatically re-aggregates metrics based on the resulting enabled set of attributes. There are four different aggregation strategies supported (`sum, average, min, and max`) which can be specified as a setting in `config.yaml`. The changes to the config.yaml are: ```yaml receiver: someMetricReceiver: ... metrics: ... attributes: [<list of attributes to include for metric at runtime>] # new aggregation_strategy: <sum|avg|min|max> # new ``` Attribute `requirement_level` takes president over this re-aggregation and any metric attribute with a `requirement_level` of `required` cannot be disabled in this way. For more information on `requirement_level` please see [13913](https://github.com/open-telemetry/opentelemetry-collector/pull/13913) The set of attributes provided by the user _must_ be contained in the set of attributes defined in the metadata.yaml, including an attribute which is not defined in the metrics `metadata` file will fail. Also, attempting to omit an attribute defined as `requirement_level: required` will cause the configuration to fail and the collector not to start. Omitting the field entirely will default to the defined set of metric attributes in the `metadata` file with a requirement level of `recommended` or above. Due to its large scope and foundational nature, a featuregate has been added for this change. This gate is represented by a new field in the `metadata.yaml`, `reaggregation_enabled: <bool>`. Setting this to `true` will enable the new codegen with spatial reaggregation features.  #### Link to tracking issue Fixes [10726](https://github.com/open-telemetry/opentelemetry-collector/issues/10726)  #### Testing Generated tests have been updated to test new aggregation behavior.  #### Documentation ran `make gogenerate` ran `make generate`

main

18 minutes ago

Merge branch 'main' into feature/configtls-insecure-cipher-suites

vignesh-codes:feature/configtls-insecure-cipher-suites

27 minutes ago

Merge branch 'main' into fix-otlp-default-balancer

tank-500m:fix-otlp-default-balancer

37 minutes ago

[xextension] Add deprecated type alias support for extensions Add support for deprecated component type aliases to extensions, following the implementation started in #14349 The new `xextension.WithDeprecatedTypeAlias` factory option allows extension authors to register deprecated type aliases using: ```go xextension.NewFactory( newType, createDefaultConfig, createExtension, component.StabilityLevelAlpha, xextension.WithDeprecatedTypeAlias(oldType), )

dmitryax:alias-for-extensions

43 minutes ago

fix spellcheck

shalper2:10726-reag

2 hours ago

Merge branch 'main' into ci/_rerun

paulojmdias:ci/_rerun

3 hours ago

Fix lint Signed-off-by: Pavol Loffay <p.loffay@gmail.com>

pavolloffay:ocb-component-schema-alternative

4 hours ago

update chloggen config Signed-off-by: alex boten <223565+codeboten@users.noreply.github.com>

codeboten:codeboten/otlp_grpc

4 hours ago

Active Branches

Enhancement: Add include_insecure_cipher_suites to configtls to enable insecure cipher suites

last run

27 minutes ago

#14043

fix: Remove remaining default configuration.

last run

37 minutes ago

#14351

-43%

[xextension] Add deprecated type alias support for extensions

last run

43 minutes ago

#14405

Home Terms Privacy Docs