Graylog Previous Solutions

Andrey Mostovykh - PeerSpot reviewer
Senior Data Architect at a comms service provider with 51-200 employees

We switched to Loggly because of the infrastructure costs of Graylog. Loggly is an all in the cloud commercial offering. Even though Graylog is free and doesn't require any maintenance and we just pay for the infrastructure, surprisingly, Loggly costs less than Graylog. So, we save money with Loggly. That was a big surprise to me.

Graylog is very stable, but Loggly is less stable. Maybe they're trying to cut costs. We have had a couple of outages, and quite often, we had indexing delays. When the data is not available right away, we have to wait for that. With Graylog, with our over-provisioning, we never had these issues, but we use Loggly because it's more efficient money-wise for our volume.

One drawback of Loggly is that they have just a few sites where they can store data. Previously, the site was only in the United States. We couldn't choose anything else. For us, it wasn't a problem because there was some agreement between the European Union or European Economic Area and the United States on data processing, but then this agreement got canceled. So, Loggly introduced one European site. They do have something over here, but we still lack support on the locality of the data because our customers are in Asia, and we want services to be placed closer to them. We want more sites. If Loggly, for example, could be deployed on any AWS instance, such as on Amazon Cloud or Google Cloud, which do have data centers in, for example, Thailand or the Asia Pacific, that would be beneficial. Loggly still doesn't have that. They are developing something, but that's an advantage of Graylog. It can be placed anywhere you have the infrastructure.

There is one particular mode with which we could not agree with Loggly, but there is some progress there. We have high traffic, but we don't want to store the data for long. Loggly suggests 90 days by default. We don't need 90 days because we need to troubleshoot situations that happened today and yesterday. We only need a couple of weeks of data, but we need to process a lot of traffic. Loggly wasn't ready for this type of load. I do understand why Loggly does that. It's not the storage that is most expensive; it's the CPU resources that you need to put into the indexing process when you ingest logs into the system. So, Graylog is more flexible because you still can tweak it to your particular load. You can say that you need just two weeks of high-traffic data, but you would need the infrastructure built specifically for this use case. With Loggly, we spent a year negotiating this mode. We came close, but it's still not ideal.

The other competitors, which we haven't had in production, such as Humio, are promising lower prices. It seems like the next generation of log processing. Graylog is based on Elasticsearch, and it seems that Loggly is also based on Elasticsearch or at least some mutated version of it. Humio seems to be based on something else. They don't have Elasticsearch. So, they don't have this burden of maintenance.

View full review »
Nicolae CIornii - PeerSpot reviewer
Security Officer at BC Energbank S.A.

We have tested IBM QRadar and now use it. First of all, the key factor is the pricing. I saw that IBM QRadar has an interactive dashboard, providing valuable insights to people. Additionally, I've seen that IBM QRadar has an agent that simplifies installations across various platforms without requiring intricate configurations. Also, IBM QRadar has automatic reporting.

View full review »
Lokesh Puthalapattu - PeerSpot reviewer
Senior Marketing Specialist II at Harman International

I have previously used Logstash. The main difference between Graylog and Logstash is in Logstash it takes a longer time for searching logs.

View full review »
Buyer's Guide
Graylog
March 2024
Learn what your peers think about Graylog. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
JC
Senior Architect at a tech vendor with 51-200 employees

Splunk, Logstash, and Elasticsearch.

View full review »
CN
Senior DevOps Engineer at a financial services firm with 10,001+ employees

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.

View full review »
it_user776922 - PeerSpot reviewer
Release Engineering Manager

I have always used Graylog2. Initially, I may have looked at Logstash and Loggly, but once it was off and running, I embraced the Graylog way of things. 

View full review »
JD
Technology Consultant

No previous solution.

View full review »
it_user774168 - PeerSpot reviewer
Systémový inženýr DS senior

There were no solution before Graylog. It was built as new project.

View full review »
BK
Network Engineer at a media company with 10,001+ employees

We are also using Zenoss.

View full review »
it_user776928 - PeerSpot reviewer
Java Software Developer at a financial services firm with 5,001-10,000 employees
JM
IT Security Consultant at a tech services company with 10,001+ employees

Splunk: The price was the factor for the switch.

View full review »
it_user805368 - PeerSpot reviewer
Software Engineer, DevOps at a tech services company with 51-200 employees
Buyer's Guide
Graylog
March 2024
Learn what your peers think about Graylog. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.