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
New Relic
Score 7.9 out of 10
N/A
New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Pricing
SolarWinds Loggly
New Relic
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
Free (Forever)
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Telemetry Data Platform
$0.25
per month per extra GB data ingest (after first free 100GB per month)
Incident Intelligence
$0.50
per month per event (after first 1000 free events per month)
Standard
$99
per month per full user (after first free full user - unlimited free basic users)
Pro
Contact sales team
Enterprise
Contact sales team
Offerings
Pricing Offerings
SolarWinds Loggly
New Relic
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
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.
It is perfect for observing our energy platforms during high-load situations, such as grid demand spikes, or our real-time ingest of sensor data, allowing us to respond in real time to anomalies. And it’s a good way to monitor API performance in client dashboards, too. But it’s not as conducive for low-budget/low-code work or deep customization that doesn’t get ample development support given its complexity and expense.
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
Capturing Front end Metrics specially web vitals and setting up alerts for violations really helps.
NRQL is great tool to fetch the data you need. With queries you can pull the data and put the data by table or by chart. You can even trend graphs and create dashboards.
Synthetic Monitoring is very helpful for proactive monitoring. You can use it for user journeys by using scripted browser monitor type or just check availability using PING type.
ASk AI is great addition that can fetch details you need with natuaral language
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.
I have not yet found any similar product that offers me this range of features to help us keep our online service fast and reliable. Besides this, New Relic is constantly evolving by adding new plugins to emerging technologies and platforms. Server performance measuring features are a key point as our user database grows.
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.
New Relic helps in observability setup for the critical environments and getting known about the issues and troubleshoot the applications and services. Alerts helps in knowing the abnormal state of the system and services, Dashboards are used for visualizing the key metrics and muting the unwanted notifications and dropping the extra data from the source.
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.
The support team has been really helpful and resolved most of the issues on time. However, for a couple of issues, several follow-ups were needed to elicit a reasonable response. The issue was deeply technical and could have been investigated only by their Architects, and bringing them into the ticket took longer than needed
The documentation was clear and concise; the only issue we ran into was custom application naming. Due to HTTPD mod_fcgid and the need for the application name to be set in php.ini (not in .htaccess or the virtual host directive) ... we had issues setting this up.
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.
Its covers all the observability aspects as well as giving us more competitive pricing models compared to other providers that's why I like to use New Relic in place of other tools. And also it introduces new Agentic AI features as well as it adopts AI in its RCA. As an observability tool it should reduce the RCA of any problem and New Relic is continuously focusing on that that's why I am preferring New Relic in place of other tools.
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.
