Setup is straight-forward & well documented.

I downloaded the Linux image from the internet, set up my server, and launched the setup. It took 10 minutes to install. During the last installation, I activated automatic system updates.

The setup process is very simple. 

I would rate my experience with the initial setup a nine out of ten, where one being difficult and ten being easy. 

It was pretty easy. The deployment is really quick, it took us about an hour to deploy the solution in our organization. 

The initial setup of Nagios Core is straightforward. We installed as per the steps mentioned in Nagios' documentation. It can be deployed in a day.

The initial setup process could be easier. For example, the setup for infrastructure monitoring is straightforward, but in the case of application monitoring, it is more complicated.

It depends on infrastructure, but normally Nagios is easy to deploy, and I could do it by myself. It usually takes two or three days, but I needed a week for one deployment. You need to install and configure everything and deploy the agents on various servers.

After deployment, you need to do periodic updates and patching. You download the latest pack from the Nagios server with the client. You can do an ATT update depending on if you have Red Hat or Windows between the platforms.

Initial setup was very straightforward. Just check the official Nagios website (www.nagios.org) for installation instructions.

The installation of Nagios Core was relatively straightforward with no major complexities. My team managed to install it within a day. Maintaining it is straightforward for us. We don't do frequent updates; it is a one-time install. The only ongoing task is occasional security adjustments, mainly related to access control. 

Nagios Core's initial setup was not difficult for me.

I set the whole thing up. It wasn't complex, it was just that I had to do a lot of planning. If you follow your plan then you won't end up in trouble. If you deviate from the plan, you are going to have trouble.

The initial setup is easy and straightforward. Deployment probably took us an hour or two and was not implemented all at once. New areas come up all the time that require monitoring so we research which plugin will be useful and implement that. It's enhanced gradually whenever we have a specific requirement. The implementation was done in-house. There is some maintenance involved, including for the upgrades. I manage the solution but there's a development team to monitor the services, around eight to 10 people. 

The initial setup of Nagios Core is not complicated, once you are used to it, it can be easy. The full implementation took us approximately three hours.

I rate the initial setup of Nagios Core a three out of five.

The tool's setup is straightforward. 

From what I heard, it didn't seem difficult to set up. It was quite straightforward.

We're still rolling out and deploying new instances of VMs that we want to monitor. It's an ongoing process.

Since its Nagios, it is a bit time consuming, but worth the effort. It took a few hours setting up the entire environment, including RRD, PHP, Apache, Nagios, PNP4Nagios, Perl, Python, OpenSSL, etc.

Nagios Core is deployed in a Linux operating system and it is simple to do. For a medium-sized infrastructure, the deployment can take a day.

The Nagios Core setup is complex, but I can handle it all myself. 

The initial setup was complex, mainly because it was in Linux and had many packages that we're not used to. I had to install them one by one on the app to configure the complication on the app that was solved to authenticate Nagios on the central app. It comes with regular users in files and in order to authenticate, you have to make a lot of confirmations, using Apache as well as Nagios. This was all very hard, and it took me a week to configure it.

I think deployment took about two weeks at the most. We did the deployment by ourselves. We have two people for deployment and maintenance.

Setup is not for the GUI lover as it requires you to perform a lot of CLI work.

A few years ago, the initial setup was complex, but now it's not. It just has some config files where you should add your host. Everything is written in the documentation.

The initial setup involved making sure that you knew what you were monitoring, where, what and how. Once this was done it was then possible to complete a default template which could be used to set up a server. As ever, the main effort in the beginning (once the product was selected) was in designing the layout. The actual setup was somewhat laborious (as I had not yet set up NagiosQL) and repetitive but once done, the housekeeping was minimal.

The installation is initially a little bit complex.

The process took several months. Originally, we were using Linux systems.

The initial setup was actually done by one of the vendors so we were one of the partners who collaborated with this for the installation. We were working together to do the installation and then they handed it over to us and then we took it over from there.

It was straightforward.

The initial setup is easy if you just follow the basic guide. The complexity comes when you want to customize it to suit your environment. For example, different plugins require different configurations. There's also another challenge in that Nagios was originally designed to monitor Linux servers but has since expanded to Windows servers as well.

It was a little complex.

I read the manual, set up a test server, and performed some tests. After our initial setup, I then added more servers and any IP device on our network that had SNP support (switches, sensors, printers and so on). It was my first time working with a Unix environment, and it didn't take so much time to set it up.

It was quite straightforward, but I would love to see an RPM package that includes all needed package dependencies.

Pretty straightforward to set up and configure basic system

The initial setup is pretty straightforward.

I can't say how long it took to deploy as we had several deployments at the same time, but it was not a problem at all. We didn't have any issues.

It is a complex software with many-many features, so the setup not an easy task.