Monitoring Master
The master console is intended for use on a central NeDi host, where only the master.pl daemon is running.
All other GUI modules except Devices-List, Devices-Status, Reports-Monitoring and Monitoring-Events should be disabled to avoid confusion.
In addition a unique theme should be selected to further distinguish this host from regular NeDi installations.
Setup
- Add remote NeDi installations to the agentlist and add the usernames and passwords to access them in nedi.conf
- Run master.pl from System-Services (only visible if Monitoring-Master is enabled in nedi.conf)
- Go to Devices-List and add detected agents to monitoring (NeDi agents are treated as devices)
- Go to Monitoring-Setup and select http or https as test
, to tell master.pl how to access the agents
- You can add a path like nedi/ as test option
, if nedi is not accessible in the root path
- Go back to System-Services to restart master.pl or wait for a 'pause' intervall to get the agents polled
Operation
- Upon first access, master.pl reads the last event with level 200 (alert) or above and all unacknowledged incidents.
- On subsequent runs only new alert-events are read. Incidents are removed from the master console, if they're acknowledged on the agent.
- Monitoring-Master shows those events and incidents with quick links to the respective agents.
NeDi Help