Frequently asked questions




Monitoring

Go to Hosts and click on the + New button to create a host

- Select a container (root for example) and a host template (default host for example)
- Insert a host name and an optional description
- Don't forget to select a notification period and your contact should be notified
- By clicking on the Create host button the host creation is finished

To activate host monitoring you have to Refresh monitoring configuration

- Click on the button with the two arrows in the top menu.

Also consider to read our beginners guide.

Go to Service and click on the + New button to create a service

- Select a host (Server 1 for example) and select service template (CHECK_HTTP for example)
- Select a notification period and your contact should be notified
- By clicking on the Create service button the service creation is finished

To activate service for monitoring you have to Refresh monitoring configuration

- Click on the button with the two arrows in the top menu.

Also consider to read our beginners guide.

When you create a new host it won't appear in the host list right away. In the head section of the host index table you will find a tab called Not Monitored, click on it and you will see a list of hosts which are not monitored.Your recently created host will be there.

To activate host monitoring you have to Refresh monitoring configuration your settings to Nagios/Naemon

- Click on the button with the two arrows in the top right section of openITCOCKPIT
- Execute the export by clicking on the green button
- wait a moment and enjoy your new monitored host

It is pretty easy to translate UUIDs in the console to their realname. You can simply pipe any command to our oitc debug shell and it will automatically recognize and translate the UUIDs.

Example:
ls /opt/openitc/nagios/share/perfdata/ | oitc debug -s

Any custom commands/scripts to check application specific metrics (from Nagios Exchange for example) have to be stored in /opt/openitc/nagios/libexec. Make sure to chmod the file to 755.

To use the new check, you have to create a new command in openITCOCKPIT at Objects Commands. Check out existing commands to get an idea of how to create new command. You can use $USER1$ as a path variable for /opt/openitc/nagios/libexec.

User settings

Reporting

Underlying technologies

Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work. It allows you to do work in parallel. In the case of openITCOCKPIT it enables statusengine to communicate with Nagios/Naemon through the statusengine worker and phpNSTA with statusengine through the statusengine broker.

Gearman-Job-Server

Provides different queues for different jobs and serves as an interface between the client (openITCOCKPIT) and the worker. It automatically assigns workers to jobs. You can view the different queues under System tools Debugging or by typing gearadmin --status in a terminal.

Gearman Worker

Processes the jobs he is getting assigned from the job server and reports back to the job server when the job is done.