-
Notifications
You must be signed in to change notification settings - Fork 524
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
Logger customization to avoid parse error #3871
Comments
The issue is this line here? You would like to change the field name? https://github.com/grafana/tempo/blob/main/pkg/util/log/log.go#L28 It seems we call that init method in main. If you would like to suggest some config options we'd likely take a PR to make some of this configurable. |
I am thinking adding some config like |
we would definitely take a PR to configure these fields if it helps you |
thank you, this will help a lot! |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. |
Is your feature request related to a problem? Please describe.
grafana/dskit#536
We are getting this error when try exporter logs from Tempo as json format:
{"index"=>{"status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [ts] of type [float] in document with id 'wsMnW5AB6IW1ExbRjrjx'. Preview of field's value: '2024-06-27T19:23:52.997740845Z'", "caused_by"=>{"type"=>"number_format_exception", "reason"=>"For input string: \"2024-06-27T19:23:52.997740845Z\""}}}}
and i notice this in dskit server config
Is it possible to configure the logger in yaml to remove ts or rename ts to timestamp to match our logging system schema?
Describe the solution you'd like
We can customize server logger to add/edit/remove default logged fields
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: