Graylog Reviews

What is our primary use case?

We use Graylog for developer login to assist developers and help them find issues faster, and for certain applications in production.

How has it helped my organization?

The centralized logs where one can find bugs quicker and find the line of code that is a problem has made us more efficient. The turn around time for production support is quite high when using this kind of solution.

What is most valuable?

Graylog's search functionality, alerting functionality, user management, and dashboards are useful. They also provide an easy way to create dashboards, and the interface is also quite easy to use.

What needs improvement?

Graylog can improve the index rotation as it's quite complicated. They need to work on that because it's quite cumbersome to manage the index rotation with all the logs. The filtering of logs before ingestion also needs a bit of work. This is because you have to write some code to avoid certain things before ingesting. As it doesn't support certain AIX versions, you need to upgrade the servers to accommodate it.

For how long have I used the solution?

I have been using Graylog for about three years.

What do I think about the stability of the solution?

Graylog is quite stable, and the only issue is the index rotation.

What do I think about the scalability of the solution?

Graylog is scalable and can be deployed in a clustered distributed environment.

How are customer service and support?

The support from the Graylog community is helpful, but they can do better. The enterprise support doesn't really cater to open-source solutions. They only support you if you are an enterprise working on a POC. If you want to do a POC for an enterprise solution, they need assurances that you'll buy their enterprise solution. 

Which solution did I use previously and why did I switch?

I have used different solutions like Nagios before. These solutions are more like manual processes where logging and viewing of logs are conducted on the server. Others like ELK are difficult to use because it isn't straightforward and requires a lot of reading. You have to learn quite a lot before using it.

How was the initial setup?

Graylog is quite easy to set up. As it comes with a prepackaged installation file, it's not complex to install and takes one to three days to deploy. If you have to study the documentation and then implement it, I think you can do it within a week.

What about the implementation team?

All implementation was handled in-house.

What other advice do I have?

Graylog is straightforward to install and easy to maintain. It also comes with alerting. But one has to be mindful of the support and disadvantages like the index rotation. On a scale from one to ten, I give Graylog an eight.

What is our primary use case?

What is most valuable?

What needs improvement?

For how long have I used the solution?

What do I think about the stability of the solution?

What do I think about the scalability of the solution?

How are customer service and support?

How was the initial setup?

What about the implementation team?

What's my experience with pricing, setup cost, and licensing?

Which other solutions did I evaluate?

What other advice do I have?

Which deployment model are you using for this solution?

What is most valuable?

What needs improvement?

For how long have I used the solution?

How are customer service and technical support?

Which solution did I use previously and why did I switch?

How was the initial setup?

What's my experience with pricing, setup cost, and licensing?

What other advice do I have?