You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data appears to be flowing to fluent-bit, but it's posting errors when sending to loki... any ideas?
Sep 14 06:53:24 ubuntu-server td-agent-bit[13650]: [2021/09/14 06:53:24] [error] [output:loki:loki.0] 192.168.15.71:3100, HTTP status=400 Not retrying.
Sep 14 06:53:24 ubuntu-server td-agent-bit[13650]: entry for stream '{city="null", country="null", job="fluentbit"}' has timestamp too new: 2021-09-14 12:53:19 +0000 UTC
"timestamp too new" - ?? The server is running with TZ "America/Central" and was showing time "6:53" when I starting pushing syslog data from my UDM-Pro to fluent-bit.
This server just has fluent-bit and loki running on it, the Grafana server is remote. If I switch the server to UTC, the errors disappear
The text was updated successfully, but these errors were encountered:
Hey, thanks for logging this and apologies for the delay in getting around to looking at it.
Try commenting out this section of the fluent-bit config and restarting the service.
Those lines run a script that converts everything to UTC, so if the data reaching Loki is in UTC it will be 6hrs ahead of the time on the server, which is possibly what's leading to this issue.
Data appears to be flowing to fluent-bit, but it's posting errors when sending to loki... any ideas?
"timestamp too new" - ?? The server is running with TZ "America/Central" and was showing time "6:53" when I starting pushing syslog data from my UDM-Pro to fluent-bit.
This server just has fluent-bit and loki running on it, the Grafana server is remote. If I switch the server to UTC, the errors disappear
The text was updated successfully, but these errors were encountered: