Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.
$79
per month/billed annually
Nexthink
Score 9.1 out of 10
N/A
Nexthink is a SaaS provider headquartered in Lausanne, that provides a digital workplace experience management software solution that combines real-time analytics, instant remediation, automation and employee feedback across endpoints and applications.
N/A
Pricing
SolarWinds Loggly
Nexthink
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
No answers on this topic
Offerings
Pricing Offerings
SolarWinds Loggly
Nexthink
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
Free trial for Standard and Pro plans for 14 days with all features.
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.
I've been managing desktops for 20+ years and Nexthink was the missing tool out of my toolbox. Just to give some perspective, if you were building and maintaining a house, Nexthink would be comparable to switching up from a hammer and nails and to full blown using a nailgun. Nexthink is a solution accelerator and a well thought out toolset to give you the customer experience at a glance. It allows for so much more visibility just with the default set of data points the Collector (agent) gathers, which is A LOT, and grants you the ability to gather even more data with remote actions. All of this evidence cuts how the "it could possibly be this" and "maybe it's that" discussions when you're troubleshooting an issue. It may not provide the exact answer all the time, but it gives you a "compass point" on where you need to start looking to resolve the issue. Also the service monitoring, activity monitoring, and critical event thresholds really empower the teams to know when a problem is happening and they can get ahead of it before the first call even reaches the Help Desk. Nexthink is a cornerstone tool in our environment for end user experience and I'm excited to see where the go next.
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.
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.
The on-premise solution can be slow at times and resource-demanding even on newer laptops. (This isn't the case with the cloud offering.)
Some useful features are only available to cloud customers.
Library pack configuration could be made easier, often these packs require some customization and it's not always clear how to get them up and running after importing.
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.
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.
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.
Nexthink had better integration and a better user interface. 1E did not have the engagement capability which is so critical to many of the actions we complete using Nexthink. Nexthink had better trending data capabilities. 1E did not capture and hold data the way Nexthink does so all data assumes you are able to pull information from all systems at any time. with remote systems it is unlikely you will capture all systems at the same time so it makes any actions less effective. this review was performed 4 years ago so 1E may have addressed some of these limitations but Nexthink has also grown and continues to add and improve on their industry-leading capabilities.
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.
SCCM proactive remediation: Automatically resolving hundreds of SCCM issues per month
Hardware: Identification of over $5m cost avoidance by seeing a lack of usage for 128GB SSDs - no need to upgrade to 256GB... coupled with OneDrive migration packs in the Nexthink library this is valuable.
