Remove excessive istio attributes to avoid hitting the dimensions limit

[dmitryax]

Add a new processor attributes/istio to drop excessive istio attributes and avoid running into the dimensions limit if scraping istio metrics is enabled.

(OTL-2117)

[rmfitzpatrick]

would it make sense to add a new value and generate each action so it's more flexible as additional attributes are (un)wanted?

[dmitryax]

Do you mean having another option in values.yaml for that?

I don't think we should add more configuration options to the already bloated values.yaml for this niche use case.

Overriding the set of attributes is already possible, just a bit more verbose, like:

agent:
  config:
    processors:
      attributes/istio:
        actions:
          - action: delete
            key: another_istio_attribute
          ...

[dmitryax]

Also, the current interface to enable istio metrics is pretty unflexible.

autodetect:
  istio: true

We can probably rethink it to be able to add this list of attributes. Maybe as a follow-up effort. Let me know if you have any ideas

[jinja2]

Yeah, it would be great if we made this a bit more flexible. Maybe something like this?

autodetect:
  istio:
    enabled: true
    # Explain why we remove these default set of attributes
    excludeAttributes:
    - attr1
    - attr2

[dmitryax]

The problem is the transition from bool value to the map in a backward-compatible way. We can try something out but I would rather do it as a follow-up effort not blocking the release

[dmitryax]

Filed this #769