DNIF HYPERCLOUD vs Graylog comparison

"The dashboard is helpful, and it creates visualizations to let staff review event data and identify patterns and anomalies."

"The solution is quite stable and offers good performance. It also works on a virtual machine. We haven't found any issues with it so far. It's been reliable."

"Great for scaling productivity for log monitoring purposes."

"I like the MITRE table, a feature I saw for the first time in the same solution. There was one MITRE tactic table, which can be used to identify threats if you have all kinds of rules enabled or if you have rules for all the tactics in the MITRE table. There are 14 tables in MITRE, and those 14 tables consist of multiple columns, tactics, and techniques. It was one of the first SIEM tools I saw that had that particular MITRE table. On that basis, you can create new rules and identify existing ones. At any point, if an alert is triggered, it will try to match it to any of those MITRE tactics. I liked that creating a workbook on MITRE business was straightforward. I also like that you can search using SQL or DQL."

"The most valuable feature of the solution is the number of EPS it can handle."

"The beauty of the solution is that you can develop infrastructure for a data lake using open sources that are separate from the licenses."

"The response time on queries is super-fast."

"Has a great search capability."

"One of the most valuable features is that you are able to do a very detailed search through the log messages in the overview."

"Graylog is very handy."

"Graylog's search functionality, alerting functionality, user management, and dashboards are useful."

"This had increased productivity for the dev and support teams, because we are directly notifying them."

"Message forwarding through the in-built module."

"The best feature of Graylog is the Elasticsearch integration. We can integrate and we can run filters, such as an event of interest, and those logs we can send to any SIEM tool or as an analytic. Additionally, there are clear and well-documented implementation instructions on their website to follow if needed."

"The ability to write custom alerts is key to information security and compliance."

"We have scaled from a single machine installation (a VM with a Graylog + ES + MongoDB) to (2 Graylog + 2 ES + 3 MongoDB). This was done smoothly with a minimal impact on logging."

"I feel that DNIF needs to invest more in marketing, considering that it operates at a very competitive speed."

"The solution should be able to connect to endpoints, such as desktops and laptops... If this solution had a smart connector to these logs- Windows, Linux, or any other logs - without affecting the performance of the connector, that would be wonderful."

"There are currently some issues with machine learning plug-ins."

"The EBA could be improved."

"I think DNIF HYPERCLOUD can implement the ability to export more than 100,000. At the moment, we can't go beyond that. So many times, if you're checking for the firewall logs and working on something related to authentication or network-related traffic, while that log count is low, the account goes beyond that. You can't restrict the logs or the amount of data you can export. It's very important for my situation. It would be better if they could increase the capacity of exports. Although there are many more types of searching in DNIF HYPERCLOUD, people still struggle to query out what they want because not everyone is good at SQL or DQL. The easiest way to query out in DNIF is using the GUI-based interface. But in the GUI interface, you can use operator calls. It gets tricky when you want to search for a specific type of event. You don't know where it will be passed and whether it will be consistent. In the initial phase, it's tough for us to use DNIF. You cannot pass every event in a stable DNIF. When we used that particular tool, we used to get those logs, but sometimes many things are not getting passed. So, we used to export the sheet or export the data into Excel and weigh the required details. In the next release, I would like them to improve the export of the columns and make the application more user-friendly. I would also like a threat-hunting feature in the next release."

"Dependency on the DNIF support team was frustrating."

"The vendor is fairly new and it's not as big as some of the international competitors. It's not a mature product. If you ask them to move data, it might take a lot of time."

"The solution's command line should be simpler so that routine commands can be used."

"Elasticsearch recommendations for tuning could be better. Graylog doesn't have direct support for running the system inside of Kubernetes, so it can be challenging to fill in the gaps and set up containers in a way that is both performant and stable."

"More customization is always useful."

"Graylog can improve the index rotation as it's quite a complex solution."

"I hope to see improvements in Graylog for more interactivity, user-friendliness, and creating alerts. The initial setup is complex."

"The biggest problem is the collector application, as we wanted to avoid using Graylog Collector Sidecar due to its architecture."

"When it comes to configuring the processing pipeline, writing the rules can be very tedious, especially since the documentation isn't extensive on how the functions provided for these rules work."

"We ran into problems with Elasticsearch throwing a circuit-breaking exception due to field data size being too large. It turned out that the heap size directly impacted this size in a high-throughput environment, causing unexplained instability in Graylog. We were able to troubleshoot on the Elasticsearch size, but we should have been able to reference some minimum requirements for Graylog to know that our settings weren't sufficient."

"I would like to see a default dashboard widget that shows the topology of the clusters defined for the graylog install."

"The solution requires a huge infrastructure and that is costly."

"Price-wise, the product is quite economical. I rate the solution's price as three or four on a scale of one to ten, where one is considered to be a very economically priced tool."

"The pricing is based on the log size."

"We're using the Community edition."

"​You get a lot out-of-the-box with the non-enterprise version, so give it a try first."

"We are using the free version of the product. However, the paid version is expensive."

"There is an open source version and an enterprise version. I wouldn't recommend the enterprise version, but as an open source solution, it is solid and works really well."

"Consider Enterprise support if you have atypical needs or setup requirements.​"

"It's an open-source solution that can be used free of charge."

"I use the free version of Graylog."

"Graylog is a free open-source solution. The free version has a capacity limitation of 2 GB daily, if you want to go above this you have to purchase a license."