Best practices for monitoring health

To ensure the health of the components in your data center environment, follow these best practices.

Overall health monitoring


	NOTE: You can view health and alerts on some monitored servers. To see what servers can be monitored, see monitored server hardware in the HPE OneView Support Matrix.

Monitoring step

Filter alerts based on severity or date to view current health issues.

GET 
/rest/alerts?filter="severity='{UNKNOWN, OK, DISABLED, WARNING,CRITICAL}'"&filter="created='{YYYY-MM-DDThh:mm:ss.sssZ}'"


	NOTE: The `DISABLED` severity is not applicable to alerts.

Related information: Activity

Get alerts for a specific physical resource type, such as server hardware.

GET /rest/alerts?filter="physicalResourceType='{physical_server}'"

Related information: Server Hardware

View the originating event(s) that caused a specific alert.

Select an alert.

GET /rest/alerts/
Get a specific alert using the alert ID.

GET /rest/alerts/{id}
Get the associated event(s).

GET /rest/events/{id}

Fix the problem. Use the recommended fix (perform a GET operation on the specific alert resource and view the correctiveAction attribute), or research the alert.

Server hardware health monitoring

A server or servers turn to a warning or critical status when something is not correct within the appliance. If a server profile has been applied to a failed server, the server profile will also be in a failed status.

Monitoring step
Use details from the alert to fix the problem. When available, attempt the recommended fix first. In some cases, additional research of the alert might be needed to best determine the fix. GET /rest/alerts?filter="physicalResourceType='{physical_servers}'"&filter="severity='{WARNING, CRITICAL}'" Related information: Activity
Make sure that server profiles are appropriately assigned to the server hardware. Related information: Create a server profile

Network health monitoring

To determine the current health of a network or networks on the appliance, view alerts for interconnects and logical interconnects to verify the correct connections. To list alerts, you can perform a GET operation on alerts and filter for alerts related to interconnects. To list states, you can perform a GET operation on interconnects and logical interconnects and filter for an OK state.

Monitoring step

Monitoring step
View alerts for interconnects. Select an interconnect alert. `GET /rest/alerts?filter="physicalResourceType='{interconnect}'"&filter="severity='{WARNING, CRITICAL}'"` Get a specific alert using the alert ID. `GET /rest/alerts/{id}` Related information: Interconnects
Filter for logical interconnects with unhealthy stacking. Get unhealthy logical interconnect. GET /rest/logical-interconnects?filter="stackingHealth='{Unknown, Disconnected}'" View specific unhealthy interconnect using the interconnect ID. GET /rest/logical-interconnects/ `{id}` Related information: Logical Interconnects
Use information provided in the alert to fix the problem. Use the recommended fix if there is one, or research the alert. Related information: Activity

View alerts for interconnects.

Select an interconnect alert.

GET /rest/alerts?filter="physicalResourceType='{interconnect}'"&filter="severity='{WARNING, CRITICAL}'"
Get a specific alert using the alert ID.

GET /rest/alerts/{id}

Related information: Interconnects

Filter for logical interconnects with unhealthy stacking.

Get unhealthy logical interconnect.

GET 
/rest/logical-interconnects?filter="stackingHealth='{Unknown, Disconnected}'"

View specific unhealthy interconnect using the interconnect ID.
```
GET 
/rest/logical-interconnects/

{id}
```

Related information: Logical Interconnects

Use information provided in the alert to fix the problem. Use the recommended fix if there is one, or research the alert.

Related information: Activity

prev	up	next
Best practices	home	Best practices for backing up an appliance