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
SolarWinds Server & Application Monitor
Score 8.2 out of 10
N/A
SolarWinds Server & Application Monitor (SAM) delivers application and server monitoring capabilities. SAM allows for self-service for easy setup, 1200+ monitoring templates, and customization options, as well as integrate with other SolarWinds products.
N/A
Pricing
SolarWinds Loggly
SolarWinds Server & Application Monitor
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
SolarWinds Server & Application Monitor
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
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.
For monitoring applications that run on Windows hosts on VMware or HyperV virtualization, SolarWindows offers a nice, vertical view of both the loads and the resources. In such an environment, this makes life really good! But if you have something else -- for example, Linux hosts -- you're on your own to some extent. That is, the things it does well, it does very well -- but everything else is much less polished.
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.
Provides basic monitoring/visibility. Visibility into detailed/fine-grained issues best suited for more specialized/expensive solutions.
Licensing per monitored application rapidly uses up purchased license count.
More out-of-the-box templates or easier setup of monitoring less-common applications would make the solution more appealing given the target audience of the product.
We are heavily invested in Solarwinds products for a reason. They are generally easy to setup and run with, requiring only some interfacing with support or help articles on rare occasions. They do what we bought them to do and we can't ask for more.
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.
SolarWinds Server & Application Monitor is quite easy to use and super versatile. It allows you to do just about anything you can through premade templates or through scripting. You can use an agent on the servers if you want to, or you can monitor through WMI or SNMP credentials. You can customize thresholds for alerting quickly, and you can configure alerts to be as complex or as simple as you want.
The graphical interface and the performance of the database leave a little to be desired, they could be better explored.Some functionality and screens do not work well depending on the browser used. The integrations never had any problems or caused crashes in other systems.
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.
I think there was only a couple times I had to open a support case for SAM and one time they got multiple engineers on the phone to get a better idea what I was trying to monitor and was able to point me in the best direction to monitor that system.
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.
It has been a while since we first purchased SolarWinds, but I looked over several other products that I can't remember now. Many other products tried to scan the network to find computers but given that our computers are located in various places across campus with other computers in our buildings that are not ours that type of network scanning was not what we needed. Other services have extra services that we had no need of and I liked the ability to add custom fields in SolarWinds so we can track the information on each computer that we need to know.
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.
Less time spent investigating causes of issues. We are alerted straight away and can find the root cause of the issue in less time.
We have been able to ditch all our previous individual monitoring solutions, none of which integrated with each other for a single solution which fully integrates with each of the different modules to provide a single portal for monitoring and alerting.
