Datadog is a monitoring service for IT, Dev and Ops teams who write and run applications at scale, and want to turn the massive amounts of data produced by their apps, tools and services into actionable insight.
$0
Up to 5 hosts
SolarWinds Loggly
Score 9.4 out of 10
Mid-Size Companies (51-1,000 employees)
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
Pricing
Datadog
SolarWinds Loggly
Editions & Modules
Free
$0
Up to 5 hosts
Log Management
$1.27
Per Million Log Events
Standard
$15/host
Up to 500 hosts
Infrastructure
$15.00
Per Host Per Month
APM
$31.00
Per Host Per Month
Enterprise
Custom
500+ hosts
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
Offerings
Pricing Offerings
Datadog
SolarWinds Loggly
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
Free trial for Standard and Pro plans for 14 days with all features.
I actually couldn't get anybody from Datadog to engage with me, the main problem we had was that our devices couldn't connect to an encrypted port, but we didn't want to send our logs in plain text over the internet. We implemented an on-net log aggregator which then connects …
DataDog Is well suited to all of the Infrastructure Monitoring Solutions, DB monitoring, and other Network monitoring also. It's not well suited because it cannot give perfect Infrastructure recommendations for our use case but also For example: If we are using AWS DB to monitor performance insights then Datadog is less effective there because AWS gives very niche recommendations.
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.
APIs, the ability to interact with the data we pull into data dog is key. We port the information over to Servicenow, so the ability to pull everything into DataDog, then Servicenow, is a key component of our success here at Wayfair.
Simple Interface - clean, useful, effective. Allows users to use DataDog for one reason, get work done.
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 had a couple "integrations" that had some issues during setup, but Support addressed them very quickly
Unnecessary alerts about DataDog components...by the time I see them, they're almost always also fixed
I wish there was a DataDog mobile app that would have dedicated alerts (configurable per alert to override Do Not Disturb setting) instead of relying on emails notifications that could be overlooked in the midst of many incoming emails around the same time.
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.
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 usually gets it right. We did have a rather complicate issue setting up monitoring on a domain controller. However, they are usually responsive and helpful over chat. The downside would be I don’t think they have any phone support. If that is important to you this might not be a good fit.
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 are still trying other products, but people still like Datadog. After setting up a dashboard, it's great for monitoring instances on Datadog. Also, the DevOps team had a good time setting up Datadog. It means Datadog was way easier to set up compared to those others.
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.
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.
