Replies: 1 comment
-
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. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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:
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.Beta Was this translation helpful? Give feedback.
All reactions