Enhance runtime input with selectors for nodes

[a-thaler]

Description As part of https://github.com/kyma-project/telemetry-manager/issues/972 enhance the current runtime input with a new selector for nodes. It should be disabled by default.

Criterias

• A new selector is added to the runtime input which will emit metrics as outlined in https://github.com/kyma-project/telemetry-manager/issues/1001#issuecomment-2154182359
• The selector can be used independent of the other selectors, if this selector is enabled only, only the related metrics are exported
• Multiple pipelines having different selector settings will result in different metrics being exported

Tasks

• Add new feature
• Verify proper instrumentation scope is in use
• Enhance documentation
• Enhance E2E test for runtime input (to assure compatibility of the emmitted metrics)

Reasons

Attachments

Release Notes

[a-thaler]

While implementing the feature we realized a serious problem. The gateway has a really nice feature of enriching all data with the typical resource attributes about the source, in case it is missing. Unfortunately, the new metrics are kubernetes resource specific and a source as this is not existent. In consequence, the resource attributes should not get enriched. In summary, we need a way to disable the enrichment on metric level. Possible solutions are discussed in https://github.com/kyma-project/telemetry-manager/pull/1409.

Most likely we will add a new resource attribute which can be added to your metrics. If the attribute is present, an enrichment will not happen.

So next steps are deciding on the solution and then introduce the conditional switch mechanism

[a-thaler]

The internals of the collector setup got adjusted and in next two weeks the actual feature can be realized on top of it. So the release will be in 2 weeks (not including rollout)