Syslog integration no longer forwarding events to Graylog
Syslog integration no longer forwarding events to Graylog
I began testing the beta version of the Linux controller back in July of this year, and since then, I have not received any forwarded syslog messages to my Graylog instance. No relevant settings or configuration were changed on either the controller or my Graylog instance. I wanted to check whether are any known issues with syslog forwarding in the beta versions of the controller. I just updated to 5.14.32.2 and the behavior has remained the same.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP thanks, but the side effect is that it broke the Syslog RFC 5424.
Anyway, I'm getting in the syslog server lines like the following from an OC200, firmware 1.34.2 (5.15.8.12).
<134>1 2025-02-13 13:04:07 DF_BCNLAB-DF_BCNLAB - - - WAN: DHCP client renewing IP succeeded. (IP-Address=172.16.24.10, Mask=255.255.255.0, Gateway=172.16.24.1)\r
Do you have any information about what those 3 hypens after the controller/site name mean? What are those 3 placeholders?
Thanks!!
- Copy Link
- Report Inappropriate Content
We released a pre-release firmware for hardware controller yesterday.
But it's with watermark.
If you don't mind, please update it and see if this firmwar helped.
https://community.tp-link.com/en/business/forum/topic/745920
digitalFounders wrote
@Vincent-TP thanks, but the side effect is that it broke the Syslog RFC 5424.
Anyway, I'm getting in the syslog server lines like the following from an OC200, firmware 1.34.2 (5.15.8.12).
<134>1 2025-02-13 13:04:07 DF_BCNLAB-DF_BCNLAB - - - WAN: DHCP client renewing IP succeeded. (IP-Address=172.16.24.10, Mask=255.255.255.0, Gateway=172.16.24.1)\r
Do you have any information about what those 3 hypens after the controller/site name mean? What are those 3 placeholders?
Thanks!!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 767
Replies: 12
Voters 0
No one has voted for it yet.