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
LogicMonitor
Score 8.4 out of 10
Mid-Size Companies (51-1,000 employees)
LogicMonitor’s SaaS-based platform, LM Envision, enables observability across on-prem and multi-cloud environments. It provides IT and business teams operational visibility and predictability across their technologies and applications.
N/A
Pricing
SolarWinds Loggly
LogicMonitor
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
Enterprise
Contact sales team
Website Monitoring
Contact sales team
Offerings
Pricing Offerings
SolarWinds Loggly
LogicMonitor
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
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.
Our platform is broken down into Pro and Enterprise Pricing. Pro includes monitoring for all of your cloud, hybrid, and on-premises infrastructure. Our Enterprise package includes all of this, plus our AIOps and Machine Learning functionality that provides dynamic thresholds, root cause analysis, anomaly detection and more!
LogicMonitor only charges by the device. What is considered a device? A device is anything with an IP address that you want to monitor, including a physical device or a cloud resource. This means multiple data sources under the same IP address can be monitored for the same price. Unlike some monitoring platforms. we don’t charge per node, interface, or metric.
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
Our business used the trial period they provided on one of our systems and conducted sessions with all of this software. Our team tested all of these software options before deciding on LogicMonitor, as our business is expanding daily and we needed a system that could …
Basically, we did not have any idea about it and how to choose, but we asked one of our former bosses, as they were very experienced with it, so they helped us by clarifying a few things between New Relic and LogicMonitor, as they told us that if you are looking for an …
SaaS monitoring makes so much sense. Why run your monitoring inside the same environment you're trying to monitor, and how do you monitor your on prem monitoring if there's an outage affecting your own infrastructure? Whilst LogicMonitor isn't a specific point solution so …
SolarWinds Access Rights Manager (ARM), SolarWinds NetFlow Traffic Analyzer (NTA), SolarWinds Network Automation Manager (NAM) and Microsoft System Center Operations Manager (SCOM)
When looking for a monitoring tool, LogicMonitor was similar or better than all of them. We moved away from SolarWinds because of its inability to monitor other network environments and lack of a collector or probe type device that could collect remote data. PRTG was very …
LogicMonitor was the most versatile and easy to deploy solution. The data from LogicMonitor could be integrated with our other platforms, so it became the source of truth.
We replaced N-Central with LogicMonitor, and had an extended bakeoff with Datadog. There were many things we liked (and still like) about Datadog, but its deployment model and less agnostic focus were disqualifying for our specific use case.
Our initial business requirements in 2016 were to monitor Vblock and FlexPod deployments. We had specific gaps with particular storage appliances the monitoring tool we used at that time could not monitor effectively. When evaluating the mentioned solutions, LogicMonitor was …
After switching from Solarwinds to LogicMonitor we would never go back. The higher price for LogicMonitor is well worth all the areas that this platform excels when compared to Solarwinds. The support is great, they are available directly through the web portal in a chat and I …
During the evaluation process we looked a number of other solutions, a detailed technically analysis was carried out to map functionlity, deployment and scalabilty across the solutions.
The primary areas that LogicMonitor succeeded are around the simplicity of deployment, …
Domotz didnt cover all devices, for example MacOS devices. Which we dont have a lot of but are still critical to monitor on our network. Solarwinds Network Device monitoring was free and great, however the display was a bit much. Also had a lot of stuff we didnt really need to …
Auvik did not provide historical data and could not monitor as many device types as LM. We found the Auvik collector to be more "buggy" and have had less issues with LM. We do feel that Auvik had a better network topology map and would clearly show device relationship. That is …
LogicMonitor has a ton more ways to customize and monitor specific processes or items that other products simply cannot do. We started monitoring applications and actually logging into them to verify everything from start to finish is fully monitored and is working properly. I …
SolarWinds had the big breach just as we left it. We loved how powerful it was, and how customizable - however, it is an ON-Prem tool, and as a growing MSP, that dynamic didn't and couldn't scale. We then moved to Auvik, which had the cleanest GUI and some neat features. That …
LogicMonitor is much easier to configure, deploy, and manage than Zabbix. Alert tuning and client configuration is clear and intuitive in LogicMonitor. Zabbix is agent based, very convoluted configuration, and is difficult to adjust tuning to minimize false positives and alert …
Solarwinds was a good tool when we were having a small amount of network devices, but once we reached to a large number of network devices, Solarwind started giving issues as it stopped respnding sometime, slowness in navigation, DB need fixes sometime etc. While the same data …
Because LogicMonitor is easy to use and not as expensive as Nagios. LogicMonitor has more functions and is more intuitive to resolve the issues raised.
LogicMonitor is a way easier to implement and keep it running than Zabbix due to the included SNMP template and the IA built in. The time to make it run is way faster.
Auvik was much more simple to use, and the graphical representation of the network topology was very useful for networking. LogicMonitor definitely has the upper hand in the amount of information you can manage, however.
LogicMonitor does config saves and netflow out-of-the-box, while other products we have evaluated did not. That is a huge advantage in my business, as we sell these two things as a service.
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.
We have several government departments and universities as our clients, and we conduct online examinations for them. Therefore, our servers require additional security to prevent unauthorized access to our systems remotely without our permission. We were performing an examination for one of our clients when someone from outside attempted to access our systems by creating a backdoor to our servers. Our team was busy handling the examination process and ensuring its smoothness. However, thanks to LogicMonitor, we were alerted at the right time, and we were able to save our data and clients' information with its help.
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
LogicMonitor is very customizable. We can build whatever modules we need, because it uses standard protocols like HTTPS, SNMP and WMI to gather data and metrics.
We like that LogicMonitor is an agentless solution for our use case. Not all customers will allow an agent-based approach to 3rd party tools.
LogicMonitor has thousands of out of the box modules, which work on their own and also act as good baselines for the ones that we will end up customizing more. We are rarely starting at zero when we decide to do something new with LogicMonitor.
LogicMonitor has great documentation, and support has been helpful in the instances where we've needed them.
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.
This product has met virtually all of our needs. It was easy to implement and has been simple to support. Customization has been intuitive with many options available. They keep adding features and expanding available options. The future of LogicMonitor looks even better than it is today which is very promising. The management and support teams at LogicMonitor are always helpful
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.
Set up is super easy. Just stand up a small Linux or Windows server to act as a collector. There are no agents to install on monitored devices and all you need is SNMP or WMI access. When creating dashboards, all you have to do is find the widget on the device you want to show up and choose the menu option to add it.
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 sales team support we received was top notch. They worked hand in hand to make sure the product met all expectations. So far we have not really had to work with support that much; we have worked with setup team after purchase to deploy product fully. No issues so far and we are four weeks in.
I did not truly dedicate myself to implementing LogicMonitor. However, I overheard the IT team members explain that "LogicMonitor is perfect for us as it has made most of the work automated, and implementation and training sessions were perfect for us." Thus, I can state that everything went smoothly with our implementation.
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.
We did not use software like LogicMonitor for the same work before, but I must say that my experience with LogicMonitor has been outstanding so far. It helps me to be free of tension. I can now concentrate on the actual work I was hired to do for my company.
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.
We have been able to eliminate multiple tools through LogicMonitor's ability to use collectors to run scripts and collect any numerical data from any reachable endpoint along with the customization and widgets available for dashboards. This has allowed for reduced costs and consolidation to a single point of view.
The ability to grant our clients access to see their data in real time has improved both our client satisfaction surveys and attributed to a few point gain in our NPS score. The ease of getting to the data has also reduced the quoting time for our sales teams during renewals to quantify what a client is consuming.
The amount of data that LogicMonitor collects affords our technicians a wide area of review when trying to isolate an issue and find a root cause. With the standard out of box data that is collected we have often been able to set a new threshold on something not previously thought of to proactively alert us in the future after identifying those root causes. This has reduced our Major Issues from 3-5 per month to usually 1-2 or less per quarter.