Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Retrieve Indicator Data API
The following external API can be used to access KPI over time statuses, KPI definitions, and indicator statuses.
The service log file is located under: <OMi_HOME_GW>/log/jboss/serviceHealthExternalAPI.log
.
Return values are supported in XML and JSON formats.
Authentication should be done using basic access authentication method. For details and examples see http://en.wikipedia.org/wiki/Basic_access_authentication.
You can use the following to get KPI over time statuses.
API Syntax
https://<Gateway Server>/topaz/servicehealth/customers/<Customer Id>/ kpiOverTime?ciIds=<CI ID>&startDate=<Start Date>&endDate=<End Date>
The API uses the following parameters:
-
customerId. Customer ID (use 1 for non-HPE SaaS deployment).
-
ciId. Mandatory; use comma-separated CI IDs.
-
startDate. Mandatory; start time for the KPI status (value representing the date in milliseconds since January 1 1970).
-
endDate. Mandatory; end time for the KPI status (value representing the date in milliseconds since January 1 1970).
-
kpiId. Optional; use comma separated KPI internal IDs as in the repository UI (default is empty for all KPIs).
The following is an example of the API and its output:
https://omi.example.com/topaz/servicehealth/customers/1/kpiOverTime? ciIds=0b656ce308022a6739e3e726497fda6a&startDate=1296499370000 &endDate=1296501466000
<kpiStatuses> <kpiStatus> <ciId>0b656ce308022a6739e3e726497fda6a</entityId> <ciDisplayLabel>ATM 1610</ciDisplayLabel> <kpiType>6</kpiType> <kpiDisplayName>Application Performance</kpiDisplayName> <timeStamp>1296499370000</timeStamp> <status>20</status> <statusDisplayName>OK</statusDisplayName> <duration>311000</duration> </kpiStatus> <kpiStatus> <ciId>0b656ce308022a6739e3e726497fda6a</entityId> <ciDisplayLabel>ATM 1610</ciDisplayLabel> <kpiType>6</kpiType> <kpiDisplayName>Application Performance</kpiDisplayName> <timeStamp>1296499681000</timeStamp> <status>-2</status> <statusDisplayName>No Data</statusDisplayName> <duration>1785000</duration> </kpiStatus> <kpiStatus> <ciId>0b656ce308022a6739e3e726497fda6a</entityId> <ciDisplayLabel>ATM 1610</ciDisplayLabel> <kpiType>6</kpiType> <kpiDisplayName>Application Performance</kpiDisplayName> <timeStamp>1296501466000</timeStamp> <status>20</status> <statusDisplayName>OK</statusDisplayName> <duration>13334000</duration> </kpiStatus> <kpiStatus> <ciId>0b656ce308022a6739e3e726497fda6a</entityId> <ciDisplayLabel>ATM 1610</ciDisplayLabel> <kpiType>7</kpiType> <kpiDisplayName>Application Availability</kpiDisplayName> <timeStamp>1296428400000</timeStamp> <status>0</status> <statusDisplayName>Critical</statusDisplayName> <duration>69663000</duration> </kpiStatus> </kpiStatuses>
The output fields are as follows:
Field |
Description |
---|---|
ciId |
CI ID |
ciDisplayLabel |
CI display label |
kpiType |
KPI ID (see Get KPI Definitions below) |
kpiDisplayName |
KPI display name |
timeStamp |
Start time for the KPI status; value representing the date in milliseconds since January 1 1970 |
status |
KPI status (see Get Indicator Statuses below) |
statusDisplayName |
KPI status display name |
duration |
Duration of the KPI's status in milliseconds. |
Return Codes
The API returns the following return codes:
Name |
Error Code |
Description |
---|---|---|
BAD_REQUEST |
400 |
|
UNAUTHORIZED |
401 |
User has no permission for the selected view |
INTERNAL_ |
500 |
|
You can use the following to retrieve the KPIs defined in the system.
API Syntax
https://<Gateway Server>/topaz/servicehealth/customers/<CustomerId>/ repositories/indicators/kpis/<kpiId>
The API uses the following parameters:
-
customerId. Customer ID (use 1 for non-HPE SaaS deployment).
-
kpiIds. Optional; leave empty for all KPIs (default), or enter a KPI internal ID as in the repository UI, to select a specific KPI.
The following is an example of the API and its output:
https://host.devlab.ad/topaz/servicehealth/customers/1/repositories/ indicators/kpis/
<kpis> <kpi> <id>1</id> <name>Legacy System</name> </kpi> <kpi> <id>1311</id> <name>Value</name> </kpi> <kpi> <id>1310</id> <name>Exceptions</name> </kpi> </kpis>
The output fields are as follows:
Field |
Description |
---|---|
id |
KPI internal ID as in the repository UI |
name |
KPI name |
Return Codes
The API returns the following return codes:
Name |
Error Code |
Description |
---|---|---|
NOT_FOUND |
404 |
KPI not found |
INTERNAL_ |
500 |
General failure |
You can use the following to retrieve indicator statuses.
API Syntax
https://<Gateway Server>/topaz/servicehealth/customers/<CustomerId>/ repositories/indicators/statuses
The API uses the following parameter:
customerId. Customer ID (use 1 for non-HPE SaaS deployment).
The following is an example of the API and its output:
https://host.devlab.ad/topaz/servicehealth/customers/1/repositories/ indicators/statuses
<targets> <target> <id>20</id> <name>OK</name> </target> <target> <id>15</id> <name>Warning</name> </target> <target> <id>10</id> <name>Minor</name> </target> <target> <id>5</id> <name>Major</name> </target> <target> <id>0</id> <name>Critical</name> </target> <target> <id>-1</id> <name>Info</name> </target> <target> <id>-2</id> <name>No Data</name> </target> <target> <id>-4</id> <name>Downtime</name> </target> </targets>
The output fields are as follows:
Field |
Description |
---|---|
id |
KPI status internal ID |
name |
KPI status name |
Return Codes
The API returns the following return codes:
Name |
Error Code |
Description |
---|---|---|
INTERNAL_ |
500 |
General failure |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: