Something could potentially be improved, though it works effectively for me. In the early stages, over 10 years ago, syslog-ng was lacking some features, so I created a patch for it. I used a patched version rather than the vanilla version. I attempted to submit a patch to the mainstream, but syslog-ng had a different implementation approach, so it wasn't accepted. A few years later, they implemented what I needed in a slightly different way, but now it satisfies my needs, and I no longer require a patched version.
It's hard to find people who know how to use syslog-ng. I often find problems with configurations, and solutions aren't integrated correctly with syslog-ng. For example, there might be data with extra decimals, or the collector agents are incorrectly named. It isn't a problem with the solution; it's a lack of professionals.
Log Management is the practice of collecting, storing, and analyzing log data from various sources within an IT environment to improve security, compliance, and operational efficiency.
Efficient Log Management allows organizations to detect anomalies, troubleshoot issues, and ensure compliance with industry regulations. Logs come from diverse sources, including servers, applications, and network devices. Handling and analyzing this data effectively can offer significant insights into system...
Something could potentially be improved, though it works effectively for me. In the early stages, over 10 years ago, syslog-ng was lacking some features, so I created a patch for it. I used a patched version rather than the vanilla version. I attempted to submit a patch to the mainstream, but syslog-ng had a different implementation approach, so it wasn't accepted. A few years later, they implemented what I needed in a slightly different way, but now it satisfies my needs, and I no longer require a patched version.
There is room for improvement in terms of observability. Additionally, a possible new feature could be Kafka integration.
It's hard to find people who know how to use syslog-ng. I often find problems with configurations, and solutions aren't integrated correctly with syslog-ng. For example, there might be data with extra decimals, or the collector agents are incorrectly named. It isn't a problem with the solution; it's a lack of professionals.
Syslog-ng isn't a true SIEM solution, and you need some expertise to get it to work in a SIEM use case.