WARNING, this is still experimental!
Introduction
The master console should be used 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.
Usage
- 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 appears there 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 to tell master.pl how to access the agents
- Go back to System-Services to restart master.pl or wait for a 'pause' intervall to get the agents polled
Details
- 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.