Replies: 1 comment
-
I had very similar issue (400 Bad requests from Loki) but with file source.
and upon examining the response from Loki, it turned out it was complaining about timestamp too new due to different time zone setting. Applying the correct timezone to the time and reformatting it properly with parse_timestamp in Vector solved the issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Im trying to ingest syslog messages from access points using the syslog source, filter for a specific message, then use loki as the source sink.
Tried various options but everytime loki just seems to respond with a HTTP 400 - Bad Request
heres my config:
heres one of the syslog messages sent to stdout by the console sink, which is correctly showing only the transformed messages:
{"appname":"WIFI-4-CLIENT-CONNECTED","facility":"user","host":"zzz-zzz-zzz-zz-z","hostname":"blahblah","message":"Client [XX-XX-XX-XX-XX-XX] connected to WLAN [MY SSID] on radio [2]","severity":"warning","source_ip":"192.168.0.2","source_type":"syslog","timestamp":"2024-05-31T16:17:21Z"}
vector log output:
I cant work out what i am doing wrong. using vector 0.38.0 and loki 2.8.0
any suggestions?
many thanks
Jamie
Beta Was this translation helpful? Give feedback.
All reactions