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
PRTG
Score 8.7 out of 10
N/A
PRTG Network Monitor is the flagship offering from German software company Paessler, for monitoring local and wide area networks (LANs & WANs), servers, websites, apps, and more.
$1,750
perpetual license
Pricing
SolarWinds Loggly
PRTG Network Monitor
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
PRTG 500
1,750
perpetual license
PRTG 1,000
3,200
perpetual license
PRTG 2,500
6,500
perpetual license
PRTG 5,000
11,500
perpetual license
PRTG XL 1
15,500
perpetual license
PRTG Enterprise
Custom Pricing
subscription license
Offerings
Pricing Offerings
SolarWinds Loggly
PRTG
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.
It is well suited for an environment that deploys networking equipment and is needing monitoring 24/7. It works well to deliver real time data and alerts that are suited for taking action and notifying groups of members. It is less appropriate for use cases that involve only a few devices that don’t have dedicated teams looking for problems or uptime.
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.
Very, very configurable. You can create all kinds of monitors for all kinds of things. Plus it has loads of suggestions out of the box. It can get complicated but monitoring is complicated. Pretty decent interface and good support - active community.
I really liked how easy it was to add alerts by SMS. So easy to setup.
I like their sizing models (for purchase). We're actually small enough that we are free. But it's not free as in stripped down - it's free because we don't use many "sensors" and don't honestly have the need.
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.
Licensing on a per entity basis can be cumbersome for devices which have a ton of monitoring points like network switches\routers. Each sensor may count against a license, which could be a lot of you were monitoring every TX\RX of an SFP for example
A better method to easily template\copy monitors across devices
The navigation in the web GUI could be a little more straightforward in terms of the hierarchy
I would renew it because the platform has brought us many technical and economic benefits that make the cost-benefit ratio very good. Additionally, to do so does not require large investments in training, licensing or infrastructure, and at the administration level, extensive knowledge is not required to be able to bear it.
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 tool is very intuitive to use and it is Windows-based (everybody knows how to use Windows) so it's easy to get into. Every time is setup in a hierarchy so if you have a good initial hierarchy design, it will really reduce administrative effort down the road.
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.
PRTG does everything we need it to do and more. Ease of use, ease of management and maintenance and clarity of monitoring of hundreds of different types of device and service gives this a large advantage over other products on the market that I have tried. I would definitely recommend it to anyone who needs a network monitoring product in their environment and even to people who don't know they need a solution yet!
It's very important that de project's teams have different member of the TI. We have learned too late the importa of Security Analyst at the design architecture moment. We have to rebuild part of the implementation for made this big mistake.
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.
PRTG offers more versatility in monitoring when compared to the other solutions we tested. The other solutions were also limited as far as customization options, which made them less adaptable to our networks. When compared to Auvik, for instance, we prefer PRTG as it offers immediate notifications through the desktop client - not limited to email notifications as with Auvik. We also appreciate the fact that PRTG can be self/on-prem hosted vs Auvik's cloud model. This makes for an easier deployment and less firewall adjustments to allow traffic to cloud-hosted solutions.
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.
The ability to analyze multiple pieces of information in one place, especially with historical data, has saved our IT department time and headaches. It would be so much more difficult to trace an issue without PRTG, just relying on event logs and an open task manager window.
The cost is not cheap, so it's an expense that hits the bottom line like everything else. Figure in hardware costs as well, ideally a server outside of your main environment.
I keep saying this, but the historical data piece is worth so much. There's really no good way to collect all of that information in one place without something like PRTG. And that definitely saves time and money in the long run.