NGOP Overview and Monitor

  Terms/Architecture
    Agents 
      watch things 
      report to NCS
      may initiate Actions
      most Agents run on monitored systems
    NCS 
      Ngop Central Server
      forwards events to Status Engines
      forwards events to Archiver
    Status Engine
      read hierarchy,rules from config files
      conclude Status from events.
      retain events over time range
      may initiate Actions
    Monitors 
      connect to Status engines.
      display information from Status Engines
    State
      Reported by Agent
      Up, Down, Unknown
    Severity 
      Reported by Agent
      Good, Warning, Error 
    Status
      Defined by Status Engine
      Good, Warning, Error, Bad, Undefined, Unknown
    Actions
      may be run locally (by agent or Status Engine)
      may be run centrally (on ngopsrv)
      parameters substitution from event
      most common: email,helpdesk ticket
  Monitor
    Web Monitor
      Uses Browser (most are supported)
      Login required [Login.jpg]
    Java monitor
      Requires Java
      runs as current user
    Startup
      Initially you choose a "Role" [Role.jpg]
        maps to a Status Engine 
        Common roles: operator, admin
      Tabbed Display		   [Display.jpg]
        Upper tabs Settings, Monitor
        Monitor tabs: Display, Action,...
      Left side:		   [Display-hier[1-4].jpg]
        component hierarchy
        [un]fold with [>] [+] buttons
    Monitor Tabs
      Display			   [Display-hier4.jpg]
        Icon for component Status
        Icon has arrow for worst Severity
        Refreshed every 2 minutes
        Examples
          Green Icon with Yellow Arrow:
          system is Good, but a Warning was logged 
          Red Icon with Blue Arrow:
          system is Bad, and a Notice was logged 
        Update from NCS button for the impatient
      Action [Action.jpg]
        Shows history of Actions for components
        Column headings are sort-by links
      Event [Event.jpg]
        Shows Events which changed Status of components
        Column headings are sort-by links
      Alarm [Alarm.jpg]
        Shows Events which maintained Status of components
        Column headings are sort-by links
      Edit:Action, Edit:Event, Edit:Alarm [Edit_Event.jpg]
        Like Action, Event, Alarm, except:
	doesn't refresh
        has checkboxes to acknowledge
      Summary
        Lists 2 layers of hierarchy
        Lists last 2 Event/Alarms for each component
        Always sorted by ID