[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [Bug 3668] New: Canned early-morning report
From:       bugzilla () opennms ! org (bugzilla at opennms ! org)
Date:       2010-03-30 23:46:12
Message-ID: bug-3668-627 () http ! bugzilla ! opennms ! org/
[Download RAW message or body]

http://bugzilla.opennms.org/show_bug.cgi?id=3668

           Summary: Canned early-morning report
           Product: OpenNMS
           Version: SVN, trunk
          Platform: PC
               URL: http://www.open-factory.org
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: webUI - Reporting
        AssignedTo: buglist at opennms.org
        ReportedBy: r.trommer at open-factory.org


This is a playground for a canned report in OpenNMS. I had a few ideas and put
all this stuff in a report.

The main idea is to classify outages. Categories are node, interface, service
and management outages.

Node outages are only nodeDown events, for example a HTTP outage, caused by a
nodeDown isn?t counted.

Interface outages, same principle only interfaceDowns counted, a HTTP outage
caused by an interfaceDown isn?t counted
Management outages, only nodeLostService from SNMP services, don?t know if
this helpful, I?m an OpenNMS admin ;)
Service outages are all other outages with nodeLostService. 

The StrafePing is totally ignored in the outage overview, just my point of
view.

If someone would like play with this stuff feel free, all stuff in the zip-file
attached to this mail. Some other ideas and more realworld experiences are very
helpful. The jrxml is prepared to be stored in
/opt/opennms/etc/report-templates.


-- 
Configure bugmail: http://bugzilla.opennms.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[prev in list] [next in list] [prev in thread] [next in thread]