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
Logstash
Score 8.0 out of 10
N/A
N/A
N/A
Pricing
LogicMonitor
Logstash
Editions & Modules
Enterprise
Contact sales team
Website Monitoring
Contact sales team
No answers on this topic
Offerings
Pricing Offerings
LogicMonitor
Logstash
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
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.
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.
Logstash is a must in an ELK stack, which I am sure is going to be the #1 case. At any point when you have several sources, Logstash can be the common point to aggregate, and categorize those data. Then send this new data to its destination. Very handy. It is free and open source. It may not be appropriate to analyze data-sets dependent on each other but from a different data source. Reason being Logstash works on data at hand, and not wait for other data to arrive. It would be unwise for Logstashh to handle complicated, long-running transformations because this is injected and ejected. The faster you do it, the safer.
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.
Memory: Logstash is a HOG, if you are deploying it on commodity (i.e. cheap and old) hardware: You will need at least 2GB, just for Logstash. So don't expect to run your entire ELK stack on one AMD Athlon machine.
Overlap: Logstash fills in an area of the ELK stack that makes the most sense: as a log file transformer / shipper. However, if you start breaking that stack, with the addition of other components- you start seeing where features of Logstash may be implemented or solved in the additional components much easier (or better, or to a higher degree of resolution)
More Overlap: Since my team employs Syslog-ng extensively- Logstash can sometimes get in the way (and this may be a problem for DevOps stacks overall): You can configure Syslog to record certain information from a source, filter that data, and even export that data in a particular format. Logstash will pick that data up, and then parse it. However, if you don't keep your Syslog-ng configuration files, and your Logstash configuration files in sync, your results will not be what you expected, and this will translate into (sometimes) hours/days of work, hunting down a line item in a configuration file.
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
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.
As I said earlier, for a production-grade OpenStack Telco cloud, Logstash brings high value in flexibility, compliance, and troubleshooting efficiency. However, this brings a higher infra & ops cost on resources, but that is not a problem in big datacenters because there is no resource crunch in terms of servers or CPU/RAM
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.
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.
MongoDB and Azure SQL Database are just that: Databases, and they allow you to pipe data into a database, which means that alot of the log filtering becomes a simple exercise of querying information from a DBMS. However, LogStash was chosen for it's ease of integration into our choice of using ELK Elasticsearch is an obvious inclusion: Using Logstash with it's native DevOps stack its really rational
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.
It is very difficult to give any figures on ROI, as it depends on many factors, and in a Telcocloud environment, it is much complex to find out; however, I would give some points below on ROI
ROI based on flexibility is very high, as it reduces the time to find RCA
ROI based on integration is very high because it supports multi-vendor environments, avoiding vendor lock-in & works across multi-cloud setups
ROI on resource consumption is less because Logstash in 2-3 times more resource-intensive as compared to its lightweight alternatives resulting in latency
