Retrieve average CPU, Memory bus, I/O bus or CPU interconnect utilization data. Accepts multiple metric types.
HPE Compute Ops Management API (latest)
HPE Compute Operations Management provides a Restful API to customers who want to manage their devices programmatically or through a command line. The API enables customers to invoke operations or tasks such as list devices, see device details, device health, and manage their device's firmware.
UPDATED API ENDPOINTS
Compute Ops Management now supports the HPE GreenLake API endpoints (<region>.api.greenlake.hpe.com). The Guide contains more information about this change.
Download OpenAPI description
Overview
License
Languages
Servers
API endpoint for US West
https://us-west.api.greenlake.hpe.com/
API endpoint for EU Central
https://eu-central.api.greenlake.hpe.com/
API endpoint for AP Northeast
https://ap-northeast.api.greenlake.hpe.com/
Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/
Query
Start date for utilization data retrieval.
start-date=2025-01-15
start-date=2025-04-01T06:00:00Z
End date for utilization data retrieval.
end-date=2025-01-15
end-date=2025-04-01T06:00:00Z
The metric type for which utilization data is to be retrieved.
Enum"CPU_UTILIZATION""MEMORY_BUS_UTILIZATION""IO_BUS_UTILIZATION"
URI of the resource for which utilization data is to be retrieved. This can be a server, filter or group URI.
resource-uri=/compute-ops-mgmt/v1beta1/filters/e7cef8e6-a3f6-4490-b669-136e3ca40617
resource-uri=/compute-ops-mgmt/v1/servers/875765-S01+1M512501AB
resource-uri=/compute-ops-mgmt/v1/groups/420372b6-af2e-464d-970d-e9339abfc74f
Limit the resources operated on by tags or return only the subset of resources that match all the filter tags.
filter-tags=('Rack' eq 'Rack1')
filter-tags=(('Rack' eq 'Rack1') AND ('Row' eq 'Row1'))
Limit the resources operated on by an endpoint or return only the subset of resources that match the filter.
NOTE: The filter query parameter must use URL encoding.
filter=entityDetails/model eq 'Proliant DL 360'
filter=entityDetails/generation eq 'GEN_10'
filter=entityDetails/processor eq 'AMD 8 core Gen 10'
filter=entityDetails/location eq 'Bangalore, KA, India'
Headers
Tenant-Acid header can be used by an MSP workspace to make API calls on behalf of their tenant by specifying the tenant's application customer ID.
In order to make such an API call, the Bearer token must belong to an MSP workspace and this header value must be the application customer ID of a tenant within the MSP workspace. Use the /compute-ops-mgmt/v1beta1/accounts API to determine the application customer IDs for your tenant accounts.
- API endpoint for US Westhttps://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/utilization-averages
- API endpoint for EU Centralhttps://eu-central.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/utilization-averages
- API endpoint for AP Northeasthttps://ap-northeast.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/utilization-averages
- Mock serverhttps://developer.greenlake.hpe.com/_mock/docs/greenlake/services/compute-ops-mgmt/public/openapi/compute-ops-mgmt-latest/compute-ops-mgmt/v1beta1/utilization-averages
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://us-west.api.greenlake.hpe.com/compute-ops-mgmt/v1beta1/utilization-averages?start-date=string&end-date=string&metric-type=CPU_UTILIZATION&resource-uri=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Response
application/json
{ "averages": [ { … } ] }