Data Services API
Data Services API (1.3.0)
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/
https://us-west.api.greenlake.hpe.com/
https://eu-west.api.greenlake.hpe.com/
https://eu-central.api.greenlake.hpe.com/
https://ap-northeast.api.greenlake.hpe.com/
Request
Returns the list of active issues for the account and user obtained from the request header. The list includes issues only for the resource-types that the user has permissions to view. Active issues are issues in the CREATED state. Clients using this API must process the returned issues for any desired groupings.
Use offset in conjunction with limit for paging. The offset is the number of items from the beginning of the result set to the first item included in the response.
Use limit in conjunction with offset for paging. The limit is the maximum number of items to include in the response.
The expression used to filter responses. You can filter on the following properties: issueType
, severity
, category
, state
, createdAt
, services
, sourceResourceId
, sourceResourceType
. You can combine multiple comparison operators using “and”. The returned set of resources must match the criteria in the filter query parameter A comparison compares a property name to a literal. The comparisons supported are the following: “eq” : Is a property equal to value. Valid for number, boolean and string properties. “gt” : Is a property greater than a value. Valid for number or string timestamp properties. “lt” : Is a property less than a value. Valid for number or string timestamp properties “in” : Is a value in a property. The property is an array of number, boolean or string properties. "contains": Is a substring value that is equal to a portion of the property value. Valid for strings. Syntax: “eq” : filter=<property> eq <value> {host:port}/data-services/v1beta1/issues?filter=<property> eq <value> “gt” : filter=<property> gt <value> {host:port}/data-services/v1beta1/issues?filter=<property> gt <value> “lt” : filter=<property> lt <value> {host:port}/data-services/v1beta1/issues?filter=<property> lt <value> “in” : filter=<property> in <value> {host:port}/data-services/v1beta1/issues?filter=<property> in <value> “contains” : filter=contains(property,value) {host:port}/data-services/v1beta1/issues?filter=contains(property,value)
- Can use and to add more filter inputs {host:port}/data-services/v1beta1/issues?filter=<property1> eq <value1> and <property2> lt <value2>
- To filter multiple values on one property e.g. filter=severity in ('CRITICAL','WARNING') {host:port}/data-services/v1beta1/issues?filter=severity%20in%20CRITICAL%2CWARNING Examples: GET /data-services/v1beta1/issues?filter=issueType eq 'ISSUE' GET /data-services/v1beta1/issues?filter=issueType eq 'ISSUE' & state eq 'CREATED' GET /data-services/v1beta1/issues?filter=contains(sourceResourceType,'orchestrator') GET /data-services/v1beta1/issues?filter='data-ops-manager' in services Filters are supported on following attributes: issueType, severity, category, state, createdAt, services, sourceResourceId, sourceResourceType
resource property to sort, with an order appended Order may only be either “asc” (ascending) or “desc” (descending)
The select query parameter is used to limit the properties returned with a resource or collection-level GET. Multiple properties can be listed to be returned. The server must only return the set of properties requested by the client. The property “select” is the name of the select query parameter; its value is the list of properties to return separated by commas.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues
https://us-west.api.greenlake.hpe.com/data-services/v1beta1/issues
https://eu-west.api.greenlake.hpe.com/data-services/v1beta1/issues
https://eu-central.api.greenlake.hpe.com/data-services/v1beta1/issues
https://ap-northeast.api.greenlake.hpe.com/data-services/v1beta1/issues
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
Issues list
The issues returned by the query.
A monotonically increasing value. This value updates when the resource is updated and can be used as a short way to determine if a resource has changed or which of two different copies of a resource is more up to date.
Details of the resources related to the issue
Severity of the issue. For issue: CRITICAL, WARNING, INFO. For reco: HIGH, MEDIUM, LOW
An auxiliary calculated attribute to help the end-user filter snoozed and un-snoozed issues
Date-time until this issue will be considered snoozed/inactive until this time. RFC 3339
Identifier for the source resource that is contained in relatedResources
Type of the source resource that is contained in the relatedResources
{ "count": 0, "offset": 0, "total": 0, "items": [ { … } ] }
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues-metadata
https://us-west.api.greenlake.hpe.com/data-services/v1beta1/issues-metadata
https://eu-west.api.greenlake.hpe.com/data-services/v1beta1/issues-metadata
https://eu-central.api.greenlake.hpe.com/data-services/v1beta1/issues-metadata
https://ap-northeast.api.greenlake.hpe.com/data-services/v1beta1/issues-metadata
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues-metadata \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "count": 0, "offset": 0, "total": 0, "items": [ { … } ] }
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues/{id}
https://us-west.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://eu-west.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://eu-central.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://ap-northeast.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X GET \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'
Details of the issue with the given Id
A monotonically increasing value. This value updates when the resource is updated and can be used as a short way to determine if a resource has changed or which of two different copies of a resource is more up to date.
Details of the resources related to the issue
Severity of the issue. For issue: CRITICAL, WARNING, INFO. For reco: HIGH, MEDIUM, LOW
An auxiliary calculated attribute to help the end-user filter snoozed and un-snoozed issues
Date-time until this issue will be considered snoozed/inactive until this time. RFC 3339
{ "createdAt": "2019-08-24T14:15:22Z", "customerId": "string", "generation": 0, "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "resourceUri": "string", "type": "string", "updatedAt": "2019-08-24T14:15:22Z", "body": "string", "category": "string", "clearedAt": "2019-08-24T14:15:22Z", "groups": [ { … } ], "issueType": "string", "lastOccurredAt": "2019-08-24T14:15:22Z", "occurrenceCount": 0, "recommendation": "string", "relatedResources": [ { … } ], "services": [ "string" ], "severity": "string", "snoozed": true, "snoozedBy": "string", "snoozedFor": "NONE", "snoozedUntil": "2019-08-24T14:15:22Z", "sourceResourceId": "string", "sourceResourceType": "string", "state": "string" }
Request
To snooze an Issue, this API should get a request with body {snoozedFor: timeperiod}. Currently, the allowed time-period for snoozing can be a day, a week, a month or infinite. Hence, the values for snoozedFor should be from this set {"DAY", "WEEK", "MONTH", "INFINITE", "NONE"}. "NONE" corresponds to unsnoozing a snoozed issue. When the Issue is unsnoozed, the snoozed_until is set to zero timestamp. If any other value is received, HTTP 422 may be returned. Also, no other parameters will be accepted in the body. The caller may get HTTP 422.
- Mock server
https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues/{id}
https://us-west.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://eu-west.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://eu-central.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
https://ap-northeast.api.greenlake.hpe.com/data-services/v1beta1/issues/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- Go
- C#
- PHP
curl -i -X PATCH \
'https://stage-developer-portal-hpe.redocly.app/_mock/docs/greenlake/services/data-services/public/openapi/data-services-public-v1beta1/data-services/v1beta1/issues/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/merge-patch+json' \
-d '{
"generation": "string",
"snoozedFor": "NONE"
}'
Details of the issue with the given Id
A monotonically increasing value. This value updates when the resource is updated and can be used as a short way to determine if a resource has changed or which of two different copies of a resource is more up to date.
Details of the resources related to the issue
Severity of the issue. For issue: CRITICAL, WARNING, INFO. For reco: HIGH, MEDIUM, LOW
An auxiliary calculated attribute to help the end-user filter snoozed and un-snoozed issues
Date-time until this issue will be considered snoozed/inactive until this time. RFC 3339
{ "createdAt": "2019-08-24T14:15:22Z", "customerId": "string", "generation": 0, "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "resourceUri": "string", "type": "string", "updatedAt": "2019-08-24T14:15:22Z", "body": "string", "category": "string", "clearedAt": "2019-08-24T14:15:22Z", "groups": [ { … } ], "issueType": "string", "lastOccurredAt": "2019-08-24T14:15:22Z", "occurrenceCount": 0, "recommendation": "string", "relatedResources": [ { … } ], "services": [ "string" ], "severity": "string", "snoozed": true, "snoozedBy": "string", "snoozedFor": "NONE", "snoozedUntil": "2019-08-24T14:15:22Z", "sourceResourceId": "string", "sourceResourceType": "string", "state": "string" }