graylog VS kibana

Graylog is an open-source log management and analysis platform designed to collect, store, and analyze large volumes of log data from various sources. Utilizing a pipeline system for data collection and processing, Graylog collects data from various sources, parses, transforms, and enriches it before storing it in a database, allowing for easy searching and analysis via the Graylog web interface, which provides a wide range of visualization options.

ERROR: Unable to access file /usr/share/graylog/data/journal/graylog2-committed-read-offset: Permission denied #2155

Graylog -- Syslog server.

Graylog is a centralized log management platform that provides two solutions - log management and Security Information Event Management (SIEM). Graylog also provides an open-source version called the Graylog Open. Graylog Open offers the core centralized log management functionality that you need to collect, store, and analyze logs data.

It looks cool, I love seeing Rust in such applications, it would even fit the use case at my work but I wonder if authors know about Graylog Open and would be interested in answering how the current UI and things on the roadmap compare with it? Would Parseable perform noticeably better than Graylog?

I would set session logs on the Vyatta and send them to a syslog (graylog) https://www.graylog.org/ and monitoring server like LibreNMS https://www.librenms.org/. You can enable session logs by using these commands:

I don't quite understand the window-logic but for logs there are things like Logstash, Loki, Graylog and probably many others that are meant to handle logs.

As mentioned already: https://www.graylog.org/

That's not ELK, you need a logging observability tool. For example Grafana Loki or maybe Graylog, which uses elastic, but is not ELK..

- Docs issue https://github.com/elastic/kibana/issues/146397

Open source, self-hosted: Prometheus + Grafana and ElasticSearch + Kibana.

Kibana is the largest open source TypeScript codebase I know of https://github.com/elastic/kibana

I remember that reading through Kibana’s source code (https://github.com/elastic/kibana) and seeing its behavior was fairly useful to get a sense of their architecture. They also use react grid layout.

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.