graylog VS kibana

There is https://www.graylog.org/ for that and many other solutions

The current school of thought is that the more consoles you have to look at, the more you'll miss. So we try to get everything in one place. Splunk is very popular in places that have the budget to spend, but functionally it's mostly a very polished ELK stack. If you're cost constrained, there are a lot of good ELK advice - mine is that a good friend of mine swears by Graylog and that's where I would start.

Graylog is quite handy for things like this: https://www.graylog.org/ You can send the logs to a Graylog server just like any other syslog server.

I export my pfsense logs to https://www.graylog.org/ which also ingests all my other logs.

Take a look at Greylog

Have worked on a similar integration project, But with Graylog SIEM and TheHive Project. https://www.graylog.org/

Graylog

Graylog for Events and PRTG for Monitoring

This is something added to v7.15 in Kibana https://github.com/elastic/kibana/pull/107894

There is an issue about this in the Kibana repository. Please share your comments and concerns there, as that can help prioritize a solution. https://github.com/elastic/kibana/issues/91637

Very odd. Sounds like this bug.

https://github.com/elastic/kibana/blob/77fe83b1a62954579e91eb03b6a5e8e3309dfe05/src/plugins/vis_type_timeseries/public/application/lib/fetch_fields.ts#L53

Issue tracking this behavior. https://github.com/elastic/kibana/issues/76521

This was a regression that popped up between 7.8.0 - 7.9.1, I think. More here: https://github.com/elastic/kibana/issues/76954

But none of that helps you as a heavy user if you have multiple tabs open and no easy way to tell what was the documentation and what the production or development Kibana instances. It is a bit of a pain point, but you can fix it with a little hack.