We performed a comparison between Grafana Loki and LogRhythm SIEM based on real PeerSpot user reviews.
Find out in this report how the two Log Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of the solution is the tool's GUI. The solution's GUI is very user-friendly."
"We are using Grafana Loki as a database for real-time metrics."
"The tool can be used in multi-cluster environments."
"The log collection feature is good and the solution is easily understandable. v"
"The solution's stability has never been a problem. Stability-wise, I rate the solution a nine to ten out of ten."
"The effectiveness of filters is pivotal for optimizing the search process and extracting the specific information we need from the extensive log data."
"I appreciate the capability to process logs from microservices and seamlessly integrate them into Grafana."
"Loki also utilizes the same service discovery mechanism as used by Prometheus. So, whatever labeled metadata you see in Prometheus, you have the exact same metadata in the Loki system. Given this level of intricacy and the attempt to address these challenges, I firmly believe that Loki deserves praise for the work."
"We have NetFlow information going into it, so we can examine a lot of traffic patterns and anomalies, especially if something stands out and is not the baseline. This helps a lot."
"LogRhythm does a very good job of helping SOCs manage their workflows."
"Provides visibility into the network."
"The initial setup process is very user-friendly."
"The initial setup is pretty easy."
"The ability to drill down and pivot from an event is one of the biggest advantage the product has compared to other things that I have seen in the market."
"The correlation engine is extremely valuable because it uses machine learning to process information from the central manager and identifies issues in the network."
"One of the main features that I like about LogRhythm NextGen SIEM is that there are a lot of pre-built pieces. Like with our AV, we didn't have to tell it how to read the logs; they already had it pre-made. So, we essentially just had to follow their guide to get the logs imported in and set up some rules for it. We've only had to manually create the parsing rules for a few of our vendors so that we could interpret the logs correctly. Most of them had already been pre-created for us."
"There is a need for some change in the alerting types of the product. In short, a few changes in the alert area are needed due to minor shortcomings."
"We encountered certain limitations when it came to alerting, particularly when dealing with specific data sources."
"The correlation of requests is not simple in Grafana Loki and can be improved."
"In Grafana Loki, the creation of metrics is not so easy, making it an area that could be made easier."
"The solution's scalability depends on the team managing the Grafana instance."
"The product must improve its UI."
"Enhancing speed could be a game-changer, and while it might vary depending on the application, it's a factor worth exploring."
"We had a well-structured dashboard with a functional query. However, an issue arose when the Kubernetes pod restarted. The statistics from our Grafana query would reset, dropping to zero and starting anew. This was particularly noticeable with linear graphs, which are expected to show consistent growth."
"I would like a more fuller implementation of STIX/TAXII so I can pull in some of the government lists without having to go implement a whole new STIX/TAXII platform."
"We have gone through a few versions which has caused a lot of instability. We have logged a lot of hours with professional services."
"We've had issues with scaling and local support."
"I would really love to be able to take some of the data and not have to export it to a CSV file, so I can pull it into Excel to turn it into some other kind of graph."
"One area for improvement in LogRhythm NextGen SIEM is that it's a Windows-based tool, and I feel it should be on the Linux operating system instead. Another area for improvement in the tool is the UI. There should be minor changes in the UI to make it better, though I like the dashboards in LogRhythm NextGen SIEM."
"We've tried to work with a couple of engineering department guys there. We've called them and called them but we never hear anything back."
"I think they probably need to, because a lot of companies are having this cloud-first strategy, where anything that's new has to go into the cloud for some reason."
"There are other security technologies outside of this SIEM that should be inside of this SIEM. I can see in their roadmap that they're trying to address a lot of these things, and have these technologies built into the solution, because there is no point in going to another vendor or opening up a second window to obtain the data that you need."
Grafana Loki is ranked 13th in Log Management with 12 reviews while LogRhythm SIEM is ranked 8th in Log Management with 166 reviews. Grafana Loki is rated 8.0, while LogRhythm SIEM is rated 8.4. The top reviewer of Grafana Loki writes "Effective for Logging, recovery from node failures is fast and single UI supports metrics, logs, and even tracing". On the other hand, the top reviewer of LogRhythm SIEM writes "The solution reduced our investigation time from days to hours and assists in managing our workflows". Grafana Loki is most compared with Graylog, Wazuh, syslog-ng, Splunk Enterprise Security and Fortinet FortiAnalyzer, whereas LogRhythm SIEM is most compared with IBM Security QRadar, Splunk Enterprise Security, Wazuh, LogRhythm Axon and Microsoft Sentinel. See our Grafana Loki vs. LogRhythm SIEM report.
See our list of best Log Management vendors.
We monitor all Log Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.