The HPE GreenLake for Wellness APIs facilitates the automation of IT operations by enabling you to monitor wellness events related to your infrastructure. To further streamline integration workflows, these APIs provide various filtering options and KPI metrics.
HPE GreenLake for Wellness (v2)
https://global.api.greenlake.hpe.com/
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/wellness/public/openapi/wellness-service/
Events
Wellness events provide health insights about your HPE products and services and show information about automatically created support cases. Wellness events allow you to:
- Identify potential vulnerabilities before they affect your environment.
- Proactively monitor the health of your HPE products and services.
- View AI-powered recommendations about events.
Request
Retrieves a list of wellness events, in descending order of creation time so that the most recent events are listed first.
Pagination— This endpoint exclusively supports cursor-based pagination, using the next query parameter.
Filtering— The following are the supported filter parameters:
condition/severitystatus/currentStatesupportCase/caseNumberasset/serialNumberproductNameserviceNameregionserviceManager/idflagarchivereadcreatedAtupdatedAt
The filter query parameter is used to filter a set of resources. The returned set of resources matches the criteria in the filter query parameter. The value of the filter query parameter is a subset of OData V4 filter expressions consisting of simple comparison operations joined by logical operators.
Retrieve events that belong to the specified serial number.
Retrieve events with severity 'warning'.
Retrieve events that belong to productName 'HPE Alletra 9000'.
Retrieve events that belong to specified services.
Retrieve events that belong to devices in the given region.
Retrieve events that belong to specified Service Manager.
Retrieve events that belong to specified Service Manager and a Region.
Retrieve events that are flagged.
Retrieve events that are not archived.
Retrieve events that contains the given number in the support case number.
Retrieve events created before the given timestamp.
Retrieve events created between the given timestamps.
Retrieve events with severity 'warning' and that belong to productName 'HPE Alletra 9000'.
Searches for wellness events that contain the given search string. A search string can include alphanumeric characters, a space character (Unicode U+0020) or a hyphen (-). Apart from space characters and hyphens, no other special characters are supported. Including an unsupported character might cause inaccurate results. The minimum length of a search string is 2 characters and maximum is 100 characters. When performing a search, it's important to use specific terms. A generic search term may cause the search to timeout.
titlecondition.categorycondition.namecondition.severityasset.nameasset.productasset.serialNumberstatus.currentStatussupportCase.casenumbersupportCase.casestatusserviceNameproductName
Note: You can use both thefilterandtext-searchparameters in the same query. If both are provided, the filter is applied first, and then text-search is performed on the filtered results.
The select query parameter is used to limit the properties returned for support cases. The value of the select query parameter is a comma separated list of properties. All properties are returned if the select parameter is omitted.
Note: Only the total property is supported.
Retrieve the total count of events for the current filter.
Specifies the number of resources (wellness events) to fetch.
The next parameter represents the ID of an event used as a pagination cursor to retrieve the next set of wellness events. The parameter must be a valid UUID and be a part of the response of the previous request.
Event ID as pagination cursor
https://global.api.greenlake.hpe.com/wellness/v2/events
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/wellness/public/openapi/wellness-service/wellness/v2/events
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://global.api.greenlake.hpe.com/wellness/v2/events \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "items": [ { … }, { … } ], "count": 2, "next": "0001b67f-9518-4d0f-9b17-70cec7763632", "total": 300 }
Request
Update multiple wellness events in a single request. Only the attributes flag, read, and archive can be updated. This is a non-atomic operation - if an error occurs while updating a resource, the operation continues for the remaining resources. Maximum of 20 events can be updated in a single request.
Request body containing list of event IDs and common updates to apply
A list of wellness event IDs to update.
Common updates to apply to all specified events. Must follow JSON Merge Patch format (RFC 7396).
https://global.api.greenlake.hpe.com/wellness/v2/events/bulk
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/wellness/public/openapi/wellness-service/wellness/v2/events/bulk
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
https://global.api.greenlake.hpe.com/wellness/v2/events/bulk \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{
"items": [
{
"id": "0908777a-788f-45da-afb8-295c626e4d14"
},
{
"id": "0908777a-788f-45da-afb8-295c626e4d15"
},
{
"id": "0908777a-788f-45da-afb8-295c626e4d16"
}
],
"data": {
"flag": true
}
}'Bulk update operation completed. Individual events may have succeeded or failed.
List of wellness events successfully updated.
List of errors for wellness events not updated.
HTTP equivalent status code for the error.
A unique machine-friendly, but human-readable identifier for the error.
{ "successCount": 2, "errorCount": 1, "successes": [ { … }, { … } ], "errors": [ { … } ] }
https://global.api.greenlake.hpe.com/wellness/v2/events/{id}
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/wellness/public/openapi/wellness-service/wellness/v2/events/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://global.api.greenlake.hpe.com/wellness/v2/events/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "id": "0001b67f-9518-4d0f-9b17-70cec7763632", "type": "wellness/event", "resourceUri": "/wellness/v2/events/0001b67f-9518-4d0f-9b17-70cec7763632", "title": "Potential increase in the frequency of reboots on Gen 9 Servers", "description": { "mediaType": "text/plain", "content": "Potential increase in the frequency of reboots on Gen 9 Servers" }, "asset": { "name": "simba-lion-king", "serialNumber": "CZJ4490026" }, "condition": { "urn": "urn:proliant:Potential increase in the frequency of reboots on Gen 9 Servers", "severity": "notice", "name": "Potential increase in the frequency of reboots on Gen 9 Servers", "category": "Firmware/Drivers" }, "status": { "currentState": "open" }, "causes": [ { … } ], "supportCase": { "id": "73695013", "caseNumber": "29160", "type": "wellness/support-case", "resourceUri": "/wellness/v2/support-cases/73695013", "createdAt": "2023-01-27T18:17:37.607Z", "updatedAt": "2024-01-09T23:37:37.607Z", "generation": 1 }, "createdAt": "2023-01-27T18:17:37.607Z", "updatedAt": "2024-01-09T23:37:37.607Z", "generation": 0, "flag": true, "read": true, "region": "us-east", "serviceManager": { "id": "0001b67f-9518-4d0f-9b17-70cec7763632", "resourceUri": "/wellness/v2/service-managers/0001b67f-9518-4d0f-9b17-70cec7763632" } }
https://global.api.greenlake.hpe.com/wellness/v2/events/{id}
- Mock server
https://developer.greenlake.hpe.com/_mock/docs/greenlake/services/wellness/public/openapi/wellness-service/wellness/v2/events/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
'https://global.api.greenlake.hpe.com/wellness/v2/events/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{
"read": true
}'{ "event": { "resourceUri": "/wellness/v2/events/0001b67f-9518-4d0f-9b17-70cec7763632", "id": "0001b67f-9518-4d0f-9b17-70cec7763632" }, "success": true }
Async Operations
Asynchronous APIs are APIs that do not return data immediately. This means you can make multiple requests at once. A high-level overview of the asynchronous API process:
- You make a request to an asynchronous API endpoint.
- HPE GreenLake returns an acknowledgment, typically a
202 Accepted, and provides a URI to the async-operation resource in theLocationheader. - HPE GreenLake continues to process the request.
- When completed, HPE GreenLake returns the requested information.