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 8.5 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
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.
We initially setup New Relic to monitor our servers/performance as well as look into the potential of having our servers log data into there as a "single source" of our data monitoring. However, we found that the logging needs in New Relic were not in line with the application …
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 …
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 …
It's a much better pricing structure for Loggly than other competitors that were closely examined. Especially if you are trying to start off small, but full-featured, and want to know that you can get everything to work together before committing to a competitor's product that …
We had originally looked into CloudWatch to monitor our resources since we have our stack built in AWS, but found that it would take additional work to setup the dashboards, alerts, and details that we wanted to see in our reports. It was worth the additional investment for us …
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.
New - relic is well suited if you want to analyse the performance of your services and you want to improve it. Integration with multiple services with same account gives a clear picture of flow of your APIs if you have micro-service architecture. New-relic is less appropriate when you want to do logging of your system. As it does not emits every single calls
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.
gives us an monitoring of all our underlying servers and also we can configure some alerts upon them like CPU and memory alerts.
Kubernetes cluster monitoring with new relic for EKS gives us and minute details of our cluster utilisation like node usage, pods memory request and limits
Network traceability for each and every request with response time analysis is great we can trace which component is responsible for generating response delay
log managements of the logs the infrastructure is generating we can view logs through there only
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.
I would like to see sort of simulator inside the user interface, that way we can send requests directly from it to test some configuration instead of setting up a test environment in our end.
It would be nice if the data ingestion can be filtered by APM's. That way we can know which application is ingested most data.
It would be nice if we could ingest logs (apache, system logs, and other logs) and correlate them with the APM.
The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.
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.
As an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.
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.
There are times I feel that the initial support is lacking. And in some cases the automated responses of not hearing anything are annoying if the reason why there has been no movement is because we are still waiting to hear back from NR support. So, i think they should loose the automation as it can seem disingenuous
It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.
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.
New Relic is the most full-featured offering that we've found, and is incredibly easy to start using with a PHP app. The New Relic agent is installed as a PHP extension so it is able to monitor and track the performance of any PHP app being run by the web server. Other tools required the installation and setup of a PHP dependency at the application level.
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.
