REST Resources
-
/ /acks /acks/{ack-id} -
/alarms -
/alarms/{alarm-id} -
/nodes -
/nodes/{node-id} -
/outages -
/outages/{outage-id} -
/outages/count -
/outages/forNode/{node-id} -
/requisitions -
/requisitions/{foreign-source} -
/requisitions/{foreign-source}/nodes/{node-id} -
/sched-outages -
/sched-outages/{outage-name} -
/stats/alarms -
/stats/alarms/by-severity
/api/space/opennms/sched-outages/{outage-name}
The following operations are supported on this resource:
- GET - Get a scheduled outage by name.
GET /sched-outages/{outage-name} | Version 1 |
This API is used to retrieve information about the scheduled outage
Sample Usage
GET /sched-outages/{outage-name}
- Accept Headers:
application/vnd.net.juniper.space.opennms+xml;version=1
<outage id="8">
<ifLostService>2017-03-16T15:26:11Z</ifLostService>
<ipAddress>192.168.26.163</ipAddress>
<monitoredService id="37" status="A">
<ipInterfaceId>35</ipInterfaceId>
<serviceType id="2">
<name>SNMP</name>
</serviceType>
</monitoredService>
<serviceLostEvent display="Y" log="Y" id="2418" severity="MINOR">
<createTime>2017-03-16T15:26:11.020Z</createTime>
<description>
<p>A SNMP outage was identified on interface 192.168.26.163.</p>
<p>A new Outage record has been created and service level availability calculations will be impacted until this outage is resolved.</p>
</description>
<host>space-000c29e5a276</host>
<logMessage>SNMP outage identified on interface 192.168.26.163 with reason code: SNMP poll failed, addr=192.168.26.163 oid=.1.3.6.1.2.1.1.2.0.</logMessage>
<parms>eventReason=SNMP poll failed, addr%61192.168.26.163 oid%61.1.3.6.1.2.1.1.2.0(string,text)</parms>
<source>OpenNMS.Poller.DefaultPollContext</source>
<time>2017-03-16T15:26:11Z</time>
<uei>uei.opennms.org/nodes/nodeLostService</uei>
<ipAddress>192.168.26.163</ipAddress>
<nodeId>5</nodeId>
<nodeLabel>192.168.26.163</nodeLabel>
<serviceType id="2">
<name>SNMP</name>
</serviceType>
</serviceLostEvent>
</outage>
Access Control
The following capabilities are required to access this API: cap_fmpm_Alarm