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.
$1.27
per month (billed annually) per host
SolarWinds Loggly
Score 5.1 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
Log Management
$1.27
per month (billed annually) per host
Infrastructure
$15.00
per month (billed annually) per host
Standard
$18
per month per host
Enterprise
$27
per month per host
DevSecOps Pro
$27
per month per host
APM
$31.00
per month (billed annually) per host
DevSecOps Enterprise
$41
per month per host
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
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Discount available for annual pricing. Multi-Year/Volume discounts available (500+ hosts/mo).
Free trial for Standard and Pro plans for 14 days with all features.
More Pricing Information
Community Pulse
Datadog
SolarWinds Loggly
Considered Both Products
Datadog
Verified User
Anonymous
Chose Datadog
In terms of usability, I’ve found Datadog significantly more approachable and powerful compared to Elasticsearch, especially for day-to-day operational monitoring. Datadog offers a much more cohesive, user-friendly interface out of the box, with built-in support for metrics, …
Datadog is an all in one solution. It has everything in one place so you don't have to go from application to application and try to figure out what exactly happened. No more stitching database errors from one third party to backend errors in another to front end errors in …
Datadog crushed the competition on price and offering more solutions in one product cutting down on implementation time and effort while ensuring that the "integration" between one of their offerings was completely compatible with any of the others. I'm sure it's not the case …
We've completely replaced New Relic with Datadog and find it easier to use and more comprehensive. Our AWS and Sentry usage will continue for now. But Datadog gives us a much broader coverage - we can monitor our AWS services and many other services that interact with them. …
Dynatrace was cheaper but, in my opinion, its setup, features, and overall user experience do not come close to what Datadog can offer, making it more of a pain to use and not worth the cheaper cost over Datadog (especially if migrating away from Datadog to dynatrace).
The first reason for selecting Datadog was of course it's pricing which is quite better in terms of competitor like Appdynamics and splunk. Second thing is versatile services which they are offering on one platform which means entire end to end services can be monitor at one …
It's a one-stop solution for all our needs whereas in other open-source tools, we have an operational overhead to keep and manage the uptime of these tools as well and also manage their versioning, upgrade, and patching cycle. Also if there are any bugs then we have to raise an …
One of the most important reason is single agent configuration for all kinds of monitoring. It also proved an auto upgrade feature of agents that reduces the overhead. It also provides range of options when it comes to data visualization and dashboards. It also provide tagging …
Kubernetes with Prometheus and other open-source options. It is prone to more toil to set up but the stack can be largely replicated in open source technologies.
New Relic was a good tool but had really pushy salespeople. They also released a product called infrastructure recently, and it was worse than their previous product (servers). The previous product was also free! Needless to say, we will not be going back to New Relic any time …
Easier to set up and integrate with other auxiliary tools. The cost was also a benefit along with self-service capabilities. We could set up Data Dog by ourselves, versus needing to bring additional consulting efforts to setup Dynatrace. Reliability of results (less false …
Ultimately, Datadog had the most already-built bridges into our existing infrastructure -- third parties that we're using for certain services are far more likely to work with Datadog than other systems. This means that, while expensive, Datadog has done a tremendous amount of …
Datadog has been harder to setup out-of-the-box compared to its alternatives, although it's graphs and dashboards have been more useful. Other tools handle individual tasks better. For example, Splunk has been the best logging tool I've used, and New Relic is great for CPU and …
It has been easier to work with Datadog for all our business needs and get things on their roadmap if we found it lacking. Currently we use a mix of various tools as they were existing prior to Datadog came. We are evaluating new offering like Datadog's latest log management to …
I am listing how Datadog is better than below chosen NotSensu - Datadog has more integrations and easy to use UI. Prometheus - Datadog Integration are more in number than, simple installation process
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.
Geckoboard has nice dashboard options, however their third party system support isn't as strong as Datadog. Geckoboard did not support all the various server and development systems we use, whereas Datadog did. Also, Datadog has better alerting and monitoring options than …
Datadog empowers us to create dashboards and visualize the state of our infrastructure in real time. It gives us control over what we want to view and how. The graphs provide deep insight into trends and anamoly detectives. These features are lacking in some of the other …
Security Onion was a much better fit for our uses at this time. The more we integrate into a hybrid environment the more need for Loggly but at this time Security Onion accomplishes our goals.
We found that Loggly is a very good balance between functionality and costs. With the ability to analyze different log files across different platforms gives it just a bit of a bigger edge compared to other monitoring systems.
Loggly proved to be very easy to set up and integrate with our existing systems without having to add extra agents or roll our own everything. Insights others give for Java performance may be better than we've seen with Loggly, but in terms of log aggregation and data insights …
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 …
We have a Nagios Log Server, however needed specialist help to get it running before it fell over, which is why we went down the Loggly route. We also use Microsoft Cloud App Security, however we find using this as well as Loggly gives us double the power to search for issues …
Loggly was a mistake. We selected it to get a cheap vendor-hosted solution up and running quickly but have come to regret the decision and should have spent the effort to set up the right tool from the beginning.
SolarWinds Loggly integrates well with other SOlarWinds products, and that is ultimately why we chose to use Loggly. LogDNA was fine for our needs, but costly for only providing logging.
Graylog would also have met our requirements, but since we then needed to run a virtual machine (with huge disk space) and also needed more work for setup and maintenance, our calculations resulted in Loggly being more cost effective. Icinga is not made for log file monitoring …
With Loggly we can manage not only AWS apps but all the apps we have (not only Cloud-based apps). It is also very convenient to add users that need to have access to a given log streams: we do not need to manage an AWS IAM role/user. And the search engine is way more easy and …
Loggly is at another level at indexing and search experience. However, since CloudWatch has the full history with least cost it is always the fallback. So if Loggly has something like S3 glacier kind of feature for keeping old logs which are least accessed with less cost, that …
I've used ELK, Sumo, Splunk, Cloudtrail/watch, Sentinel. You get what you pay for. If you have the time, expertise, and budget for a Splunk setup, you can't beat it. ELK is great for OSS shops but takes more hand-holding to scale and stabilize. Loggly, for us, was closer to …
Loggly was the easiest to use and the one that really allowed us to get a full view of what's going on with our services, and proactively solve problems.
I honestly didn't shop around that much. I came from CloudWatch, which though it has been improving, was very frustrating when it came to just setting up a simple alarm when a specific log message is found, or extracting useful metrics from logs. Loggly was recommended to me by …
Price and ease of deployment were huge factors in our decision to use Loggly. Loggly is actually within reach for most companies while also being very easy to setup. Elasticsearch, for instance, had wildly outdated documentation when I was previewing all these tools so I was …
I have used EFK stack (ElasticSearch, Fluentd, and Kibana) and Splunk. Solarwind Loggly is the most flexible managed service out of these solutions and suitable for companies embracing the SaaS model
A one-stop solution for everything you need. Multiple functionalities are tailored to meet specific business needs. Logs are essential for any business, and Datadog manages logs effectively. Rum sessions are something new to me and have given us a new perspective on how to reverse engineer issues that we see for our customers.
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.
Modern: Loggly is modern: Dashboards, realtime information and the ability speak many different data sources and environments makes it an attractive choice
Configurability: Loggly gets log parsing right: by allowing you to in real time- filtering of log data, tagging and identifying data sources
DevOps friendly: Loggly is very Componentized: You can have an instance of Loggly running that will Monitor your Linux instance, in addition to all of it's services, as an example. Also, you can start/stop Loggly, without affecting your other components
Alert windows cause lag in notifications (e.g. if the alert window is X errors in 1 hour, we won't get alerted until the end of the 1 hour range)
I would appreciate more supportive examples for how to filter and view metrics in the explorer
I would like a more clear interface for metrics that are missing in a time frame, rather than only showing tags/etc. for metrics that were collected within the currently viewed time frame
Once the logging limit is exceeded, there are no logs period. Unexpectedly noisy logs often correlate with services misbehaving and potentially leading to disruption. An outage is an awful time to lose visibility into the entire system of apps. Some ways to bridge this gap would be appreciated.
Filtering by tags is not intuitive in the web interface. You may believe that you are performing the same search and filter as last time since the tags entered are the same, however, this is often not the case. The reliable way to know that you have the same filter is to bookmark the URL. This lack of ease in usability results in devs using Loggly less than they could and implementing logs less effectively during development time (since they don't consider themselves likely to view them anyway).
Would like to see a way to onboard our less experienced devs to using Loggly effectively.
Datadog's user interface is quite friendly and easy to navigate. With menus clearly categorized, and ability to bookmark important dashboards, one can easily find what they're looking for. For dashboards, ability to move and resize visualizations and group them, is really helpful to organize dashboards. Automatic suggestions from Datadog for important visualizations based on the metrics and logs would provide another level of ease of use.
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.
I selected Datadog because of its features and the wide range of integration support. As I already told it supports more that 600+ integrations which helps and organization to keep everything in a single place and also its AI feature which is reducing the time for root cause analysis. Its custom dashboards features which helps us to visualize the data in a more attractive way.
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 to Loggly over encrypted UDP. In theory Loggly made this particularly easy providing configuration snippets for most of the common log services (e.g. rSyslog, syslog-ng). Unfortunately the documentation was out of date and none of the provided configs worked, fortunately they were close enough that combined with our own syslog-ng experience we were able to get it up and going relatively painlessly. The choice then of going with Loggly, backed by an industry favourite in Solarwinds was a no brainer.
Loggly has alerted us to several bugs, ranging from major to small to "would have been a major problem under load."
It's great having our disparate logs collected and the alerts we have set up around them let us know recently that somebody used an incorrect document to generate a mass email. Users were trying to log in with the link provided but getting 401s and I have an alert configured to tell me about high numbers of 4xx errors.
Metrics and alerts around metrics have given us peace of mind that automated fulfillment systems aren't going off the rails and costing us hundreds of dollars.