Schema for signals arriving in collector, list of all available attributes?

[mildmojo]

Is there a way I can dump a list of all attributes attached to each log/metric/trace arriving in a collector? Some of these depend on the sender's configuration, and when I'm debugging missing attributes, it's often difficult for me to figure out:

1. What attributes are available from the receiver (as transmitted by the sender)?
2. What attributes exist after the processors execute?
3. What do attributes look like at an arbitrary point in the list of processors?

For instance, I'm currently trying to find the client IP address attribute for metrics arriving at the OTLP gRPC and HTTP receivers. Deep in the attributes processor docs, they suggest this could be available as client.address, but that doesn't work in my environment. I'm pretty sure this attribute exists somewhere, but it would be easiest if I could debug the keys and values in the processor pipeline.

[mildmojo]

I found the docs on General Attributes which may help with my direct attempts at finding the client IP address, but there are other cases where I'd need to find existing or missing attributes managed by receivers or other processors.

[CaptainPickles89]

If you're looking for a clear view of what your collector is receiving to check against attributes you could setup a seperate debug pipeline that uses the OTLP receiver and then send straight to debug, file exporter or prometheus exporter to have an unfiltered view of the telemetry you are receiving.

pipelines:
    metrics/debug:
      receivers: [otlp]
      processors: []
      exporters: [debug]

This would allow you to see what's coming in and work it out that way if that helps.