-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Timestamp Mismatch when Ingesting logs to Loki #21054
Comments
Hi @shiblisec , Can you share the |
Hi @jszwedko , Yep, that was the problem the timestamp was string instead of the timestamp datatype, did the type formatting and its working fine now. Closing this as resolved. |
Hi
and this is my remap for example:
still Grafana is showing a different timestamp while the actual timestamp on the log mentions a different time. |
I think you don't want to use |
A note for the community
Problem
I have been gathering data from multiple sources and then using vector to transform the data, I have remaped the
timestamp
fields for all my data sources, so now only one key identifier exisitstimestamp
for all my data sources. When I am ingesting the transformed logs into loki using the following sink configuration.I am getting the following results on Grafana, as we can observe the Grafana is showing a different timestamp while the actual timestamp on the log mentions a different time.
Configuration
No response
Version
vector 0.40.0 (x86_64-apple-darwin 1167aa9 2024-07-29 15:08:44.028365803)
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: