SolarWinds Loggly vs. Logz.io

SolarWinds Loggly is great for capturing and organizing logs from 3rd party sources such as NGINX. Without SolarWinds Loggly it's really difficult to manage the logs overtime, find traffic patterns, and identify issues before they become a problem. Anyone who is routinely searching through massive log files could quickly benefit from the SolarWinds Loggly and it's capabilities.

Incentivized

Logz.io is an effective solution if your alerting needs are fairly straightforward and you don't need long-term retention of logs with easy access. If being able to maintain easy access to logs longer than this is necessary, another solution might be better. If you need a high degree of precision with alerting triggers and the ability to suppress alerts, you will need to combine Logz.io with an integration to get this or you might consider a different solution.

Incentivized

• Putting our logs in one place and making them searchable. We use AWS, and CloudWatch has always been a little frustrating in this regard (though it has gotten better recently).
• Deriving metrics from our logs. I think log-based metrics is such a good idea because your logs are the ultimate source for truth in regards to what the hell is going on inside your app. I have really loved the simplicity with which I can just count certain statements and call that a metric because just through the normal course of development certain log statements just naturally become a straightforward recording of an event having occurred.
• Alerts. I actually have a few complaints about email alerts, but just the way I was able to set them up so easily has been huge. Since we started using Loggly, there have been at least 3 bugs that Loggly exposed that were frankly very bad. And withoutt Loggly or without a user reporting them, we would have never known they were happening! This is stuff I tried to set up in CloudWatch in various ways, but because of my own ignorance or perhaps the complexity/limitations of CloudWatch (or the complexity of my stack?), I wasn't getting the information that I needed until I was able to just tell Loggly to send me an email whenever the word "error" showed up.

Incentivized

• Well documented and easy to set up.
• Their alerting mechanism is really great especially when it comes to application monitoring.
• Our data analysis in Kibana is made easy with the solution for Logz.io.
• The issue checking and fixing is escalated quickly and is reported in time.

Incentivized

• Not all searches are intuitive.
• We have to use a log aggregating device to ship our logs to Loggly as our network devices can not connect on an encrypted protocol. I would prefer if we could use some sort of VPN-based connector to ship logs securely.
• Sometimes when drilled down, it can be difficult to fully reset a search term to back all the way out of a drill down.

Incentivized

• Its price can be very high, so you should have good control of it to avoid exaggerated figures.
• Some functions can be confusing.
• It has limits to create subaccounts, which is a big problem for large companies.

Incentivized

Management is not open to having an agent sending the data to the cloud instance.

Incentivized

Loggly's easy setup, very good customer support, and intuitive interface make Loggly very easy to use. User access management is also very easy as we can tailor the experience for each of our developers to access the information they need without having to wade through other information. While there was a slight learning curve in how to view the logs the way some specifically wanted, everything was possible and quite easy to do.

Incentivized

I initially struggled trying to ensure the correct data was returned in the Kibana search, but I found it overall easy to use. Some of the UI is not as seamless as I'd expect, like changing the environment completely resets your search criteria and filters, which is annoying since it's a common use case to search something in multiple environments

Incentivized

The support team have been great when we have logged tickets or had issues, most of the time it is down to user training, however we have had a couple of bugs that they have been able to iron out for us.

Incentivized

Their support team is the best in the world! They supported us in most of the critical times and helped to resolve the issue in real time. Also their email support is well maintained and never a mail is missed unanswered. Kudos to the support team of logz.io for maintaining professionalism.

Incentivized

It has good architecture, which focus on ese of use.

Incentivized

We were using Zabbix. While it is an open-source solution that you can install for free the following things were limitations of the solution. 1) The scale and uptime of the solution are now your own problem. Since we were hosting at AWS this meant we still had a cost of the AWS solution. 2) The product is complicated from a configuration standpoint. In order to get anything meaningful out of it, you had to invest a lot of time and effort. We did consider NewRelic. I have experience with that product and do think that it is a solid alternative. Ultimately experience with the simplicity and speed of deployment with Loggly encouraged me to suggest using this again.

Incentivized

Logz.io is more affordable, less work to maintain, and has more features. It was an easy choice. After my last team had to manage their own ELK stack, this was a no brainer. It helps us be focused on our core competencies.

Incentivized

• Unfortunately, we hit our logging cap on a weekly basis and we lose logs after that.
• We have lost logs after hitting the maximum during service outages. We have become accustomed to not being able to rely on having them, then things go poorly.

Incentivized

• Be capable to efficiently identify problems
• Efficiently investigate issues and find the root cause
• Be able to improve the logging of services and products

Incentivized