The main objective to use Nagios Core 4.x is to save significant costs on Infrastructure Monitoring without compromising the monitoring parameters.

So, deploying Nagios Core 4.x  was the only option for me considering the below-listed positive factors.

1) Working on Nagios Core for more than 10+ Years.

2) Good Hands On skills to cover the standard monitoring parameters such as CPU, Memory, Storage & Running Services.

3) By introducing NCPA Agent, further monitoring became very smooth & saves time as NRPE & NCPA Client Side Configuration takes more time. On the other hand, NCPA Installation is very straight & you just need to provide a unique token only.

4) NCPA Agent is available for Windows & Linux like OS environments with most of the current & previous stable kernels.

5) Presently, more than 500+ nodes & 2500+ services are under active monitoring.

The monitored services are as follows.

1) Windows & Linux Nodes

* CPU Utilization (%) & Allotted CPU Cores.

* Memory Utilization (%) & Allotted Memory (MB/GB/TB)

* Total Storage Utilization, Allotted Storage Space & Available Storage Space (MB/GB/TB)

* Running Services, CPU & Memory Utilization (%) by a particular service.

* Start the monitoring service if Nagios finds it SHUT.

2) Cisco Nodes (Switches, WLCs, APs, Routers)

* CPU & Memory Utilization.

* Bandwidth Utilization (Combined & on individual interface as well).

* Cisco WLC: No. of connected APs, CPU & Memory Utilization & Bandwidth Monitoring.

* PING RTA, Jitter & Packet Loss.

* Temperature, Free Interfaces, IOS Version, Switch Stack Status.

3) Services

* DNS/Domain Name Expiry

* SSL Expiry

* Many More...

I use this solution to monitor my network. There are 25 agents in my country. This solution sends me notifications if any equipment is down.

It's deployed on-premises. I'm currently using version 4.3.3.

There are five people in my company who use this solution.

Our company is sales based and we offer a test service to our enterprise-level customers. We use the solution to monitor our test servers and have 25 users throughout our company. 

My main use cases include monitoring of servers and services. Some of them are outside our network and some are inside the network.  

We use Nagios for one of our customers to monitor all the servers, firewalls, routers, and cameras. While monitoring the server we get alerts, this enables us to raise a ticket and notify end users that we are aware of the issue before they need to notify us.

We have 80 people using the dashboard and getting the alerts. Depending on the number of servers, routers, and firewalls we are monitoring in current clusters. When one cluster goes down, it will automatically take data from another cluster. 

We support 24/7 because our client is a financial company, if the critical servers go down, they would face financial issues. 

Our primary use case for this solution is an APM for application performance monitoring. For example, we deployed the solution on-premises so we could observe the solution. We look at the threats at the web containers, the data source, and all these components under this monitoring.

We use Nagios to monitor networking infrastructure and services.

I use Nagios Core for basic monitoring of my systems and services.

Our primary use case is for Infrastructure monitoring.

It's monitoring all of our production environment and alerting us to any issues that might pop up.

Our primary use case is for monitoring the security of our environment. We have specific services running on our Windows systems and Nagios provides us with notifications regarding the status, whether things are running properly or not. Sites hosted on IIS can also be monitored. We are customers of Nagios and I'm an infrastructure lead. 

We are using Nagios Core mainly for servers. We check the network hardware connectivity. We check for the availability of the network and for hardware failures.

We have deployed Nagios Core on a VM and it's working very well. The specs of the VM are very low because it doesn't require so much storage

We use the product to monitor server applications. 

It is used for monitoring services on a bunch of virtual machines.

In terms of the version, we're fairly up to date. We are perhaps not the most up-to-date, but we're fairly current.

We use Nagios to monitor hundreds of CentOS cloud servers (and a few Legacy Windows servers). Nagios is monitoring well over 5000 service endpoints. Some plugins were handwritten in PHP, Perl, Python, Java and Bash.

We use Nagios Core to detect any issues in our infrastructure, software, system service, and network issues. It is a centralized monitoring service.

I'm primarily using Nagios Core to monitor infrastructure like servers, virtual machines, and telephone usage like IP-DECT antennas. I don't use all of Nagios Core's data functionality. I only use the monitoring features.

We used Nagios Core to monitor our servers in other countries. Our main server is in Cairo, while we monitor other servers in Germany, which are hosting Jenkins and other web services to make sure that the infrastructure is stable and if anything goes wrong it reports it automatically.

We primarily use the solution for monitoring ops for computers and our server. We're considering adding other device monitoring as well and at points of sale.

We use the solution to monitor our IT infrastructure, like servers, the network, and things like that.

• Monitoring the critical services and network environment for a large multi-site company. 
• It is also used for troubleshooting issues and capacity planning.

The primary use for this solution is basic network monitoring of a MPLS network.