What is our primary use case?
So my use of Exabeam was primarily focused on ingesting logs from multiple web services. The current product is designed for our organization, which involves managing multiple web services and microservices deployed on different servers. Previously, before utilizing Exabeam, we had to manually log into each server and search for the existing logs. Tracking all the logs for various web services, whether in production or in other environments like pre-production, was a challenging task.
To address this, we incorporated Exabeam agents, both collector agents for Windows servers and Linux servers. This allowed us to collect all the logs on a single platform. If we needed specific logs for a particular service, we could directly access them on the Exabeam Cloud.
The problem I was facing was with the user interface (UI) when trying to identify the exact services and server names.
What needs improvement?
The problem I was facing was with the UI when trying to identify the exact services and server names. The UI's left panel was not as informative as I expected. Often, when we needed to retrieve specific information or details, the UI provided a lot of information along with filter criteria. Without the filter criteria, we had to make certain changes in the Exabeam UI. For example, there were three options available to display logs: raw, execution, and view. When selecting "raw," we obtained comprehensive information, but some details were repetitive, such as the server name, service name, method, and agent activities at different times. Although we could access this information, it took time to identify the exact log statement, especially in the case of exception-related log statements. Determining the timestamp at which a particular log was ingested posed a challenge.
This improvement will assist our developers in precisely identifying their logs. Even though you have provided a bar to create a customized dashboard for verifying logs of any service, there is still a problem. If a log is generated on the production server, let's say at 8:30 PM IST or at the present time, it takes a few seconds to be ingested into Exabeam Cloud. However, in the company, Exabeam always shows repetitive logs if my log file hasn't been generated. For example, if nothing has been logged or no action has been performed on the application for the past two hours, my log file will be empty. But still, by default, the agent collectors will check the specific location we configured for log ingestion. If that location doesn't contain anything, the logs are displayed on the screen by default. This is why we need to filter and search through numerous timestamps to find the exact location of our logs.
For how long have I used the solution?
I have used Exabeam Fusion SIEM for over a year and a half.
What do I think about the stability of the solution?
The stability of the product is best. I would rate it a nine out of ten.
Buyer's Guide
Exabeam
May 2026
Learn what your peers think about Exabeam. Get advice and tips from experienced pros sharing their opinions. Updated: May 2026.
894,738 professionals have used our research since 2012.
What do I think about the scalability of the solution?
I would rate the scalability a seven out of ten. So there's room for improvement in terms of scalability as well.
The application is also scalable without any issues. However, when you add more and more filtering criteria, the application tends to slow down.
Previously, there were almost 100 users using this solution.
How are customer service and support?
Exabeam provided great support and helped us overcome any problems and obstacles we faced, especially when we had issues with the agent collector installation on a server. I'm happy with the support provided.
How was the initial setup?
The setup is not difficult. It was easy. The documentation provided on the Exabeam documentation website was already there, so that was perfect. I didn't face any issues with that. The only challenge I had was figuring out how to find or filter the criteria to locate my exact log, as sometimes there are keywords or messages that are forwarded.
So, if I mention a forwarder with a specific IP address or server address, it gives me a whole bunch of logs that are already there. It would be great if I could access my latest or earliest logs.
There are many filter criteria available. I can retrieve logs from one hour, two hours, seven days, or twenty-four hours ago. But having logs in real-time would be very helpful. Real-time logs would be beneficial.
The reason I mention real-time is that, in ELK or Splunk, we don't face any issues when it comes to finding the exact log. They create a separate area where you can directly search for logs using keywords.
However, in Exabeam's filter criteria, we need to use key-value pairs to match specific logs or services. For example, if I want to create a filtering criteria based on my service name, I need to specify the key as "service name," followed by a colon and the service name in double quotation marks. Similarly, with "forwarder: server address" I can locate logs for a specific service deployed on that server address.
The platform is perfect. There are no drawbacks or major issues. However, enhancing the UI with minimal filtering criteria would be really helpful. We should focus on improving the UI screens where all the logs are displayed.
What other advice do I have?
I would recommend using the solution. The reason is when I approved the use of Exabeam; my client was facing issues managing logs deployed on different servers. So I suggested migrating all the logs to a single platform. They agreed, and we started exploring options, eventually choosing Exabeam. Now, my client exclusively uses Exabeam for log management.
But the only problem is that the UI is not very impressive. The UI lacks the ability to easily access all the necessary information. For example, when searching for specific keywords related to my service name or service address, the search results take some time to provide an exact match. It can be frustrating when the response time is slow.
Overall, I would rate the solution a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.