From OpenNMS
Distrubuted Pollers ToDos
- Make a webstart app
- Put webstart app buliding in the build
- Pull the appropriate poller pieces apart from the whole of opennms
- figure out communications with the main part of opennms
- figure out how to pass a configuration to a remote poller
Distributed Monitor Use Case Ideas
Terminology/Model
✓Medical Center == Monitoring Area
✓Facility == Monitoring Location == Monitoring System == Remote Poller
Application == External App == Monitored App
check == test ==
Proposed:
<!--THIS IS GOOD -->
MonitoredApplication
defined by a collection of monitoredServices
MonitoringLocationDefinition
LocationMonitor instanceof MonitoringLocationDefinition
LocationMonitor monitors 'a collection of monitoredServices'
LocationSpecificStatusChange
LocationMonitor
MonitoredService
PollStatus
User View Use Cases
1. Summary of Monitored
Need to show a table of all LocationMonitors and the computed aggregated status of each MonitoredApplication
from the perspective of the LocationMonitor
Input: none
Output:
Summary Table
For each LocationMonitor
- The 'Area' attribute of the MonitoredLocationDefinition for this LocationMonitor
- The 'Name' attribute of the MonitoredLocatoinDefinition for this LocationMonitor
- A cell containing for each MonitoredApplication that has the following attributes:
- The contents of the cell contains the number of intervals in the last 24 hours in
which all monitoredServices for that Location monitor are UP diveded by the total
number of intervals written as a percentage
- The color of the cell is as follows:
Green all monitorServices for the LocationMonitor are up
Yellow at least one monitoredService for the LocationMonitor is in warning state but none are in failure state
Red at least one monitoredService for the LocatoinMonitor is in failed state
Blue the LocationMonitor has failed to report in / is unavailable
2. History
Show the response time history for the MonitorServices of a given MonitoredApplicatoin over a given time span from the perspective of a given LocationMonitor
Input:
A LocationMonitor id, an MonitoredApplicationId id, a timeframe, and a subset of the intersection between the set of monitoredServices belonging to the LocationMonitor and the set of monitoredServices belonging to the MonitoredApplication
Output:
A GraphPage that contains:
- The current LocationMonitor
- The current MonitoredApplication
- The current Timespan
- The list of requested MonitoredServices
- A list of Graphs each containing a url to a responseTime graph as described in 3.
3. Create a graph image for the responseTime from a given LocationMonitor
Input:
LocationMonitor
MonitoredService
Constraint: The monitoredService must be a monitoredService for that LocationMonitor
Output:
Graph Image of responseTime for that monitoredServices as reported by that LocationMonitor
4. CurrentStatus page
Show the current status of a given MonitoredApplication from the perspective of a given LocationMonitor including reponseTime
Input:
A LocationMonitor and a MonitoredApplication
Output:
A table of current results returned from the LocationMonitor for monitoredServices that belong to the MonitoredApplication
5. Define/Configure a new MonitoredApplication
Some way to define the set of monitored services associated with a MonitoredApplication
6. Define/Configure a new MonitoringLocationDefinition
Define/Configure the polling configuration associated with a MonitoredLocationDefinition
Set the 'Area' for a MonitoringLocationDefinition
set the 'Name' of the MonitoredLocationDefinition
Set up the details for what MonitoredServices should be associated with LocationMonitors for the MonitoredLocationDefinition






