-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/filelog] attributes.log.file.name attribute field not found when operated on within filelog stanza #29696
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @GuyAtTheFront, I found this in documentation here:
Can you try again using
|
Hi @crobert-1, can confirm your suggestion works. Thank you! I'm not a golang developer (yet), so I can't make sense of why behavior would be different under the hood. Leaving this to owner / community to decide it the issue should be closed. Edit: (Clicked the wrong button, re-opened for owner / community to decide) |
I think this was done to remove ambiguity in the structure of JSON data with periods, and this is specific to the functionality of the Stealing and modifying the example dataset from here:
This is valid data that could potentially be operated on, so there needs to be a way to differentiate sub-fields vs. full key names. This syntax was chosen to simply be able to differentiate |
Component(s)
receiver/filelog
What happened?
Description
attributes.file.log.name field not found when move/copy operators are applied to said field
Expected Result
Since this datapoint is injected by receiver/filelog, it should be configurable at this point and not require enhancement by downstream receivers / processors.
Actual Result
field not found, error in log output below
Collector version
v0.88.0
Environment information
Environment
OS: Ubuntu 22.04
OpenTelemetry Collector configuration
Log output
Additional context
The text was updated successfully, but these errors were encountered: