Actually I'm wrong when i said nodes under default Surveillance category such as Production or Switch are generating correct availability reports. They are similar.

Surveillance Category: Switches

Outage MTTR Outage Outage Availability
Count (hours) Hours Percent Percent

test_node.com 1 158.08 158.08 94.092 5.908
Average 1.00 158.08 158.08 94.092 5.908
Maximum 1.00 158.08 158.08 94.092 5.908
Minimum 1.00 158.08 158.08 94.092 5.908

Hi, I'm very new to Opennms so please forgive my ignorance. I've installed Version: 1.10.7 on Centos 6.3 and recently had issues with customized Surveillance categories are not showing the right information (http://opennms.530661.n2.nabble.com/SLM-categories-not-updating-correctly-td6497803.html#a7582131).

But at the moment, i see negative values when i try to generate a report of Node availability for the nodes part of those customized surveillance category. Although I've other nodes which are part of default Surveillance category such as Production or Switch and they are producing correct format of availability report.

Any thoughts ?

Great, I'll drop it in and test it out. Thanks!

Aha! here it is:
One event with eventuei = 'uei.opennms.org/nodes/nodeDown'
generates one outage (with different outageid) for each service in the node
If it has two interfaces with ICMP, the query will return two outages, instead of one.
Look at it:
opennms=# select outageid, svclosteventid from outages where svclosteventid = 1089265 and outages.serviceid=1;
outageid | svclosteventid
----------+---------------- 74896 | 1089265
74893 | 1089265
(2 rows)
....

And finally I've got a solution:
@@ -101,8 +101,8 @@
END AS
outage_counter
FROM

• (SELECT

• outages.nodeid,
  + (SELECT DISTINCT
  + outages.nodeid, outages.svclosteventid,
  least(('$P!{DS_START_TIME}'::TIMESTAMP + '$P!{DS_TIME_RANGE}'::INTERVAL), outages.ifregainedservice) as ifregainedservice,
  greatest('$P!{DS_START_TIME}'::TIMESTAMP,outages.iflostservice) as iflostservice
  FROM

Hope this help!

I haven't seen a bug for that, but this also solves a negative availability issue in node availability reports.

Thanks!

Youre right I overlooked "events.eventuei = 'uei.opennms.org/nodes/nodeDown'"

I'm getting duplicated records anyway for the "outages_scope" subquery:

nodeid | ifregainedservice | iflostservice
-------------------------------------------------------- 10 | 2011-08-12 15:42:37-03 | 2011-08-12 15:40:28-03
10 | 2011-08-12 15:42:37-03 | 2011-08-12 15:40:28-03

I'm investigating a little, and will update soon.
Thanks!