Open bloodmc opened 7 months ago
Hello!
I can confirm that. We want to forward the logs from our Windows Server to a Windows loggingserver. From there, the logs should be sent to Loki using Promtail.
We have also used the custom WECs from https://github.com/palantir/windows-event-forwarding/tree/master/windows-event-channels, and Promtail crashes with the above-mentioned error message as soon as a forwarded event is being read.
However, this happens regardless of the eventchannel. It doesn't matter whether the forwarded logs are written to the custom WECs, the default ForwardedEvents Channel, or directly to the system log of the host. As soon as Promtail is confronted with an entry originating from a machine other than the host, it crashes.
Switchted to the new Grafana Alloy. This works with forwarded events.
Describe the bug Platform: Windows Server 2022 Promtail: 2.8.11
I'm using custom windows event channels from https://github.com/palantir/windows-event-forwarding/tree/master/windows-event-channels
Promtail randomly crashes as its pushing logs which seems to be related to the custom event channels I am using. The only way to get the promtail service started is to wipe out all the bookmark xml files. Note: Custom event logs are successfully being pushed into Loki but over time promtail stops working and crashes.
To Reproduce Steps to reproduce the behavior:
scrape_configs
to use custom event channels.Expected behavior Promtail to not crash while pushing custom event logs to Loki.
Environment:
Screenshots, Promtail config, or terminal output
Here is the
promtail.yml
configHere is the error when promtail crashes
https://gist.github.com/bloodmc/ac39021d6342da61a9f7f53acb93ed48