Skip to content

Unify resource attributes handling with generic attribute handling #41235

Open
@lahsivjar

Description

@lahsivjar

Component(s)

connector/signaltometrics

Is your feature request related to a problem? Please describe.

With the introduction of optional config param in #38830 the different behaviour of resource attribute's include list and attributes handling can be unified. The attributes have 3 different modes for customization:

  1. default_value: configures attributes to ALWAYS be present in the output. If the attribute is not present in the input the default value is used as the value of the attribute.
  2. optional: configures attributes based on the input. Basically, copies the attribute as-is to the output. If attribute is not present then output also has the attribute missing.
  3. No special identifier: configures attributes based on availability in the input. If the attribute is missing in the input then the event is not processed. If it is present then it is added to the output as is.

Describe the solution you'd like

Unify the resource attribute and other attribute handling.
As part of the unification, we should drop the include_resource_attributes configuration (which was used as an include list) in favor of resource_attributes configuration.

Note that this will be a breaking change.

Describe alternatives you've considered

No response

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions