What is your primary use case for LogicMonitor?

We primarily use it for unified observability, network compliance, and the benefit of an easy-to-administrate SaaS-based solution.

We use the solution for network monitoring.

We installed LogicMonitor as a SaaS-based solution, and we have an agentless approach. We are monitoring the overall interface and not just the network devices. I am looking after the network devices only.

We use it as a primary monitoring tool for our cloud offerings. I work for one of the largest service providers in Australia and their cloud solutions. We monitor the entire cloud solutions using LogicMonitor.

It is a complete infrastructure monitoring tool. It can be used to monitor your network devices, your servers, et cetera. It is a good tool, actually.

We are a network of hospitals using the solution to monitor our network devices and all of the interfaces connected to them. It's predominantly instances of applications running on Windows Server. We use the Windows WMI for Windows Server stats. The IT directors at our hospitals use it, so we have around 90 end-users Some of them have extended the monitoring capabilities to printers to stay on top of toner supplies. In the past, we've had admin people freaking out because the printer is out of toner, and we have any in the closet. Nobody was watching that, and some people would be hoarding supplies.

LogicMonitor is predominantly used in modern cloud monitoring tools. You have servers that you want to monitor for performance, CPU, memory, and so on, or you have a cloud environment that you want to monitor for EC2 instances, ALBs, and more. Our LogicMonitor keeps track of everything. LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem.

We're using LogicMonitor as a software as a service subscription to help us manage and monitor all of our network devices, as well as a lot of our Windows environments. LifePoint has around eighty different hospitals that we manage, and they all have network devices and connectivity to our corporate data centers where the applications are hosted. We're constantly monitoring the state and health of their network and just making sure that if a fiber seeking backhoe cuts a fiber, that we can know about it and get the respective vendors involved as quickly as possible.

I use it every day. We are a small MSP in the Netherlands. We have about 90 customers, and they have a lot of on-prem hardware such as servers, switches, voice systems, and devices. We monitor their environments making sure that everything is working fine. We monitor the hardware and the software performance, basic use, and things like that. It is a cloud product. You have your on-prem LogicMonitor agents called collectors, and they send all the information to the cloud of LogicMonitor. You can view the state of everything there. It seems Amazon hosted on the backside, so it should be a public cloud, but I am not sure.

Sparx Solutions is a managed service provider. We primarily use the LogicMonitor platform for monitoring, maintenance, and management of our managed services and customers' infrastructure. In terms of management, it is more around monitoring and alerting. That is essentially the core component that we use it for. However, there are other features integrated into the platform that we get value out of. We have baked LogicMonitor into our core services, in terms of MSP and managed service offerings. We use this tool to fundamentally provide network monitoring services to our customers. It is definitely a great tool and something that we use daily. We have multiple users using these solutions. They are technicians and engineers. Essentially, they use this platform for different purposes. So, a support resource will be able to use it to identify alarms and when there is a new ticket that needs to be created to remediate a problem. Engineers may use this platform to obtain valuable insight into the systems that they are working on, e.g., if they would like to understand whether a device has a really high CPU before they plan a change, etc. There are different use cases for using the platform. One of the main use cases is having users use the platform to provide support services. We deploy probes, which are hosted by us. These connect back to the LogicMonitor platform in the cloud.

We are a managed service provider and deploy LogicMonitor to support our customer base and monitor assets in the network. We use it for monitoring our customers and alerting them when something happens. We also use it for dashboard reporting, both performance reporting and end-of-month reporting. We are now moving to use the platform with API connectivity to our new billing solution, to enable both-way billing updates. What that means for us is the ability to create an order, have the monitored endpoint in LogicMonitor created, and also feed back into the billing system so that we can invoice our customers correctly. LogicMonitor is a cloud-based application and there is a small appliance installed on-premises to act as a collector. It's the device that talks to the cloud and is the intermediary talking to all the devices inside the network.

We use it for monitoring our customer networks, for monitoring network devices, and we also use it for monitoring our hosted environment. We're a managed service provider. We have LogicMonitor deployed so that we not only have our devices input into the system, but we also manage a lot of resources for our clients in it. We have it set up so that they can only see their items in there, through a lot of access control. We have a local presence with the collectors, the polling stations, while the data resides in the cloud. Once we pull the data, it then shifts all the data up to the cloud for long-term storage. LogicMonitor is all SaaS-based, other than the local collectors.

We use it to monitor the performance and health of all our internal IT systems in our data center as well as our customer equipment that we have out on customer sites. We have our own stuff in our own data center, but we also have hundreds of devices out on our customer sites where we need to monitor and manage the health and performance of them.

If I summarize LogicMonitor, it is a single windowpane. You don't have to run four hardware stats and software stats on multiple screens during the monitoring of services. It gives you flexibility. It has the capability to pull up your data sources as well. So, it is like a single window, where you can see all your resources recorded, e.g., what value are you deriving out of your software? We have our own product that we are specialized in. We needed something to help us with the setting up of the monitoring part. Our customers are very happy. They are running Dell EMC hardware, so they don't need a Dell EMC monitoring window and our software windows. With LogicMonitor, they can see what is happening inside Dell EMC in a single, unified view that completely monitors their alerts.

We use LogicMonitor to monitor our customer environments. Some customers opt to look after their own environments, but some customers have us monitor them for them. We use it to monitor the availability of servers and of network hardware. We have some storage array networks that are being monitored by it as well. We really use it as a guide to help. We monitor all of the key components in the different environments that we have running under LogicMonitor, and we use LogicMonitor as an early-warning system. If a problem develops in a customer environment, and we're monitoring it with LogicMonitor, then we get fairly rapid notification that there's a problem so we can start looking into it and doing something about it. Also, along with all of that monitoring comes a lot of information logging for things like bandwidth, so we can see how much data is coming and going over different links. If a customer came to us and said, "We're thinking about downgrading the network links that we have," we have evidence to present to them to say, "Yes, it's okay to do that because you're hardly using the network link." Or we can say, "We wouldn't advise you to do that because we've observed that you're using most of that link and, if anything, you need to increase your bandwidth." The device numbers being monitored is definitely on the order of several hundred among our three or four dozen customers. We're probably monitoring 50 different environments.

We are a managed service provider, so we have a wide range of deployments. LogicMonitor, as a whole and software as a service solution, is deployed with collectors on-premise, which also ties directly into cloud providers. We primarily monitor Citrix environments for customers. That varies from the delivery side, so network Citrix ADCs as well as virtual desktops and the supporting infrastructure around that. That's probably our primary use case. While we do some NetFlow capture for other managed service clients, the primary use case would be Citrix monitoring.

We are in four public clouds. We are in AWS, Azure, and GCP. While we do Oracle cloud, we only have a small footprint there. We are monitoring all the virtual server environments as well as all the services in those environments and alerting on various set points depending on what it is: virtual, server and service. We are also monitoring our colos. We have on-prem hardware, networking, and server solutions that we are monitoring with LogicMonitor. We are in both the cloud and on-prem. The breadth of cloud and on-prem that we have is a good use case for LogicMonitor

It is to monitor our customer’s infrastructures. We provide the service as part of our managed service offerings. We monitor our customer networks and infrastructures for things, like availability, vital statistics, and the various services, that they have running in their environments. We provide a NOC and Service Desk that actually responds to alerts that come up and use the tool to allow them to be proactive in looking after their environments.

The biggest things are infrastructure monitoring and alerting. This is mostly for our virtual machines, but it is also for other networking equipment and a few other pieces as well. We are at the newest update. It is a mix between on-premise Collectors and their software as a service (SaaS), which is the newest update. Our Collectors are also on the newest version right now. While they don't have to be the newest version, they tend to get pretty close to the newest version to work properly.

We are using the solution for on-prem, all our applications, and network monitoring. It fits everything. We use it for monitoring and reporting on our ESX, Pure Storage, Cisco, F5, Palo Alto environments. We also use it for alerting, graphing, and capacity planning. We use it for everything. We are using the latest version. We have LogicMonitor Collectors onsite in our data center, but the dashboard and everything else is all the cloud model. We use both AWS and Azure as our cloud providers.

We use it to make sure that proper tuning is done for the existing monitoring. In addition, our university has a number of schools and each is a customer of the main IT organization that manages and provides support for all the colleges, like the law school, the business school, the medical school, the arts school, etc. The goal, and one of the main use cases that we were planning and thinking about, was to be able to onboard all the devices, all the applications, all the databases, as required by individual schools. We also wanted them to be able to create their own dashboard, tweak it, manage it, delete from it, and add to it. It's deployed as a SaaS model. LogicMonitor is out in the cloud.

We use it in a few different ways: * For general monitoring of operating systems. * Leveraging some customized offerings, specifically for creating application monitoring. * Some external site-to-site monitoring in various places, ensuring that our websites and external pieces are available over an Internet connection.

Right now we have two or three clients that have medium to large data centers, and we use LogicMonitor to give us an overview of the status of the infrastructure: if there are any holes or any issues either with memory, CPU, or storage devices, such as how much storage is consumed. One of them is an insurance company which has a presence here in Puerto Rico and in the U.S. It employs about 5,000 people and has two data centers in Puerto Rico and two more in Florida. Their main data center is in Atlanta with disaster recovery in North Carolina. That one is what I would consider a large environment. We also have a medium-size company in the communications area here in Puerto Rico and has about 2,000 employees. It covers all of Puerto Rico. We monitor their infrastructure in terms of servers, storage, and backups, among other things. We are also monitoring things such as vCenter, its data infrastructure, and NetScaler networking cards. We have a complete overview of the health of the client at a specific moment. We're using the SaaS solution. Everything resides on the LogicMonitor cloud. We just have connectors to extract the data from different servers that we have.

We use it for alarming on Cisco Voice systems, the Unified Communication stuff. We monitor all the gateways, trunks, SIP trunks, servers, and make sure all of the application is functioning, calls are being completed, and that there are no performance issues on the network or the voice system.

We provide IT services to other companies. We use LogicMonitor to monitor our customers', and our own, IT infrastructures, regardless of where they're hosted.

We host data centers and transit providers to enterprises, other hosting providers, end-users, and so on. We utilize LogicMonitor for monitoring our infrastructure and for monitoring our servers for some of our software on a proactive basis. We like the depth of LogicMonitor given that it can alert us to problems before they happen, rather than after they happen. We'd like to be more proactive than reactive. Our collectors are hosted on-prem and we're using LogicMonitor's SaaS platform for our results.

LogicMonitor is a monitoring solution and we monitor all our infrastructure, up to the application level. We developed additional data sources in the tool, which is a kind of customization. We have a Big Data infrastructure, a Big Data solution for semiconductor and electronics companies. We stream a huge number of files into a central location. We load them and we process them. The engineers have a type of client-based analytic tool. Using LogicMonitor, we monitor the full process of the data stream: data loading, the ETL process, the SQL database, and Big Data solutions like Vertica and Hadoop. It's a SaaS-based solution. We deployed it across all our infrastructure, which includes on-prem and cloud: AWS, Azure, and Google Cloud.

As an MSP, we are monitoring our customers' systems and whatever that might include, from servers to network devices, databases, and software; pretty much anything that can be found within current IT environments. We monitor thousands of devices in our portal at the moment.

I work for a managed service provider. We use LogicMonitor to monitor our customers' environments. There are probably about 30 customers who have their environments monitored by LogicMonitor. This allows us to get good visibility over different environments. If there are any issues, then it creates alerts. It also syncs in with our ticketing system, so it will create a ticket which is then assigned to an engineer to look at the issue. Customers can log into LogicMonitor and see their own environment, and we can login to see all our customers' environments.

We use it internally for our own monitoring and to monitor applications. We use it to monitor our infrastructure and our client's infrastructure. We are using the latest version.

We have a network that comprises a bunch of Windows Servers, Linux servers, CentOS, and a variety of network devices, such as Cisco routers, Cisco switches, Riverbeds, and some VeloCloud. We use the service to monitor and alert us to any potential issues that we may be having. We also use it to do some pink tests and to monitor the availability of some websites as well. The whole purpose is to give the IT team a heads-up, before the user base is aware of an issue. There are different levels in the system from "warning" up to "critical" that can let us see that a situation might be developing, that we might be having a problem with a system. We can proactively take care of it before it transitions to a level where it might affect our users and prevent them from doing their daily work.

We use this solution for monitoring servers in our datacenter. It performs pretty well and affords us in-depth troubleshooting capabilities.

We are an MSP, and we use it for our customers' environments: on-premise, hybrid or cloud. LogicMonitor is our backbone regarding proactivity and reporting.

Monitoring our customers' infrastructure, servers, network equipment, UPS, websites, etc., and integrating this with our ITSM to generate tickets.

We use this product internally for monitoring our on-premise infrastructure and soon to monitor our Azure infrastructure. We also use it as a service provider and we offer monitoring as a service to our customers.

We monitor Windows Servers, Linux Servers, firewalls, a variety of network devices, Active Directory, websites, etc.

We are an MSP. The product is for our managed customers to monitor their equipment and network servers. It does what it is supposed to do.