Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following tables represents theproperties of an Enterprise ServiceOutage.


Property

Description

Example

id

A globally unique Enterprise Service Outage ID

"63576103ad794974594a1f11"
namechange_idThe name of the Enterprise Service. This is used for identifying the Enterprise Service"John Test"
descriptioncurrentA long description of the Enterprise Service"This is a test Enterprise Service"
node_namedescriptionThe name of the node that is created and/or used to store the status and events for the Enterprise Service."john_test_ES"
frequencyHow frequently the status of the Enterprise Service is recalculated.60



last_updatedstart

The time that these status metrics were last recalculated. The metrics are updated with a frequency of frequency seconds.

1682489067
overall_statusendThe Overall Status can be Up, Degraded or Down. The Overall Status of the Enterprise Service is calculated from the worst of the Node State, Interface State and Service State."Down"



interface_statenodesIf any Interface is marked Down, the Interface State is marked Down, otherwise it is Normal."Normal"
interface_statuselementA decimal number between 0 (bad) and 100 (good) inclusive representing the status of the interfaces in the Enterprise Service. 
The Interface Status is calculated from the status events for the Interfaces by aggregating all the Interface-related status event levels and averaging them out to a value from 0% to 100%.
100
interface_status_leveloptionsA status level categorizing the interface_status, into traffic light colours."Normal"
interfaces_reachableA count of the number of interfaces that are reachable or null if there are none.null
interfaces_unreachableA count of the number of interfaces that are unreachable or null if there are none.0
node_stateIf any Node is unreachable, the Node State is marked Down. If any Node is reachable, but it is not at its optimal level/health, the Node State is marked Degraded, otherwise it is Normal."Down"
node_status

A decimal number between 0 (bad) and 100 (good) inclusive representing the status of the nodes in the Enterprise Service.

The Node Status is calculated from the status events for the Nodes. It aggregates the status event levels and presents an average of 0% to 100%

98.3333333333333
node_status_levelA status level categorizing the node_status, into traffic light colours."Minor"
nodes_upA count of the number of nodes that are reachable or null if there are none.1
nodes_degradedA count of the number of nodes that are degraded or null if there are none.1
nodes_downA count of the number of nodes that are down or null if there are none.1
nodes_totalA count of the total number of nodes in the Enterprise Service or null if there are none.3
service_stateIf any Monitored Service is marked Down, then the Service State is marked Down, otherwise it is Normal."Down"
service_status

A decimal number between 0 (bad) and 100 (good) inclusive representing the status of the interfaces in the Enterprise Service.

The Service Status is calculated from the status events for the Services. It aggregates the status event levels and presents an average of 0% to 100%

0
service_status_levelA status level categorizing the service_status, into traffic light colours."Fatal"
services_degradedA count of the number of monitored services that are degraded or null if there are none.0
services_reachableA count of the number of monitored services  that are reachable or null if there are none.0
services_unreachableA count of the number of monitored services that are unreachable or null if there are none.1

Limitations

API Endpoint





Limitations

API Endpoint

All requests are made under the following base All requests are made under the following base URL:

Code Block
  http[s]://server/omk/opChartsadmin/v2v3/enterprise_servicesoutages


Examples of how to use the API can be found in the response blocks below.  In general, the queries will look something like this: 

...