-
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
Character encoding issue in logs #32000
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @psneha716, do you know what encoding the logs files are in? You can set the expected encoding value using the |
@psneha716 any update on this issue? did setting the encoding fix the problem? |
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. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/filelog
Describe the issue you're reporting
I've been trying to send logs from my ECS cluster through opentelemetry collector. Some of the characters are not displaying properly in the logs, seems like some encoding issue. Is there any way to fix it?
"\u0006stdout\u0010�������\u0017\u001a�\u00172023-12-14 03:10:49,602
The text was updated successfully, but these errors were encountered: