Improve documentation for Opentelemetry inputs

[heliapb]

Relevant telegraf.conf

[[inputs.opentelemetry]]
    tagexclude = ["service.instance.id" ]

Logs from Telegraf

N/A

System info

Telegraf 1.30.3, CentOS 7

Docker

No response

Steps to reproduce

It would be beneficial to have in the sample.conf for opentelemetry an example how to drop any of the opentelemetry attributes. I was able to do it with the tagexclude as I show in the conf, but was not very straightforward to do. As the documentation seemed to point into using fielddrop, but didn't work for opentelemetry attributes, even those get turned into prometheus labels.

I don't mind adding an example or two for my use case, as I used Java Auto instrumentation with a service, and then used the existing telegraf to collect those metrics.

Expected behavior

N/a

Actual behavior

N/a

Additional info

No response

[srebhan]

@heliapb we do have a general documentation on how to modify data. I don't think it is reasonable to repeat this in the 200+ input plugins. If you do have suggestions on how to improve the general documentation and/or make stuff more discover-able, I'm happy to hear your suggestions!

However, adding general options to the sample.conf file is not what we should do, think about cases where we add (or deprecate) a general option, who should modify all plugins?

[telegraf-tiger]

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you!