get a full list of all attributes per resource with full qualified attribute name e.g. from metadata.*, auth.*

[cforce]

Component(s)

processor/attributes

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

The attribute processor allows to map, filter, rename etc attributes - but its hard to get an overview, about what attributes which are available or guess correct names.

Describe the solution you'd like

The feature request is about to bake a dictionary (yaml, json) which can be queried via endpoint so you get all available attributes per resource. Those can be used to validate or create UI to draft pipelines

Describe alternatives you've considered

No response

Additional context

No response

[github-actions[bot]]

Pinging code owners:

• processor/attributes: @boostchicken

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Hello @cforce, is there a reason that using the debug exporter to view attributes on the telemetry you're interested in is not sufficient for your use case here?

It seems like your use-case is for debugging to make sure your rules are being applied correctly, so this isn't something that would need to be available as an endpoint forever while the collector is running, from what I can tell.

[github-actions[bot]]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/attributes: @boostchicken

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[cforce]

I was more looking for a structured list /format that i can reuse as export for external documentation and validation. A export/format which follows a schema like yaml/json

[github-actions[bot]]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/attributes: @boostchicken

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions[bot]]

This issue has been closed as inactive because it has been stale for 120 days with no activity.

[cforce]

please reopen:

"I was more looking for a structured list /format that i can reuse as export for external documentation and validation. A export/format which follows a schema like yaml/json"

[atoulme]

This is too big of a report. Agreed we can do better to discover message content, but there is no guarantee of attribute presence on payload. You can use the debug exporter or the remotetap processor to see the traffic and make changes. I know that's not ideal ; your help in discovering use cases and drafting simple paths to make this simpler is welcome.

In the mean time, we're working hard to document our metrics, attributes and resource attributes as part of our receiver documentation as most of the metrics we generate are now following semantic conventions.

Please advise as to one or more concrete directions you want to take from here ; community members, please upvote this issue if you are affected and care for this experience.