Outages crossing report time boundary counted fully in SNMP Interface Availability Report

Description

When running this report (defined in SnmpInterfaceOperAvailabilityReport.jrxml) if an interfaceOperDown period begins before the start of the report's time period, then the full duration of that quasi-outage is counted in the report's output. For instance, if one ran this report for the month of May and there exists an interfaceOperDown event for a given interface on 23 April that does not resolve with a corresponding interfaceOperUp event until 07 May, then the downtime for that interface in the report would be 14 days.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Matt Brozowski October 13, 2011 at 3:35 PM

Haven't been able to reproduce this problem. If you can provide a database and an example of the report please reopen.

Donald Desloge September 6, 2011 at 12:31 PM

Any word on that DB dump? Also, that support ticket has been closed.

Jeff Gehlbach August 23, 2011 at 2:36 PM

Looks like a re-surfacing of the issue reported in https://mynms.opennms.com/Ticket/Display.html?id=96

The timing of this issue coincides closely with my wrapping up a week at that client's site, and I seem to recall Pedro raising some reporting issues in the week after. You might reopen and ping that ticket to see whether he's still seeing this problem. I believe he'll be leaving next week for two weeks' vacation, so if you need a DB dump it'd be best to get it this week.

Donald Desloge August 23, 2011 at 12:21 PM

Jeff,

Is this currently an issue, I thought I had fixed something like this a while back. If its still an issue, do you have a database that I can test with that has interfaceOperDown and interfaceOperUp events?

Cannot Reproduce

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 19, 2011 at 11:29 AM
Updated January 27, 2017 at 4:20 PM
Resolved October 13, 2011 at 3:35 PM