-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
log processing failed for unknown operator id post upgrade from 0.47 to 0.73 #27022
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Team, Just to clarify here is the exact error, which we are unable to resolve 2023-09-20T12:45:06.233Z error helper/transformer.go:110 Failed to process entry {"kind": "receiver", "name": "filelog", "data_type": "logs", "operator_id": "move2", "operator_type": "move", "error": "move: field does not exist", "action": "send", "entry": {"observed_timestamp":"2023-09-20T12:45:05.434274957Z","timestamp":"2023-09-20T12:45:05.390206283Z","body":"2023-09-20T12:45:05.390206283Z stdout F {"SeverityText":"Information","Message":"Executed endpoint \u0027.HistoryAsync ( ..test.API)\u0027"}","log.file.path":"/var/log/pods/test-7d766db845-bxngp_1eb5a1a0-2087-4f86-98eb-eb8312bea0fc/test/0.log","logtag":"F","run_id":"0","stream":"stdout","time":"2023-09-20T12:45:05.390206 |
The error indicates that one of the
In any case, the entry does not appear to have any attributes when it reaches the move operator that reports the error. Please let me know if there is any indication that this is a bug. Otherwise, I hope this is helpful information for troubleshooting your configuration. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm closing this as there does not currently appear to be any action to take. Please reopen if necessary. |
Component(s)
receiver/filelog
What happened?
hi team,
i'm facing issue with parsing the log as we upgraded out otel collector from 0.47 to 0.73.
we don't have operatorid as move2, but still we are getting operator it and log processing got failed with error i attached in log output.
there is extra attributes also added as part of logs. can you please help me?
thanks.
Collector version
0.73
Environment information
kubernetes
OpenTelemetry Collector configuration
Log output
Additional context
logs format also affected post upgrade.
The text was updated successfully, but these errors were encountered: