List active issues

get/data-services/v1beta1/issues

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.

Securitybearer
Request
query Parameters
offset
integer

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.

limit
integer [ 1 .. 100 ]
Default: 10

Use limit in conjunction with offset for paging. The limit is the maximum number of items to include in the response.

filter
string

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= eq {host:port}/data-services/v1beta1/issues?filter= eq “gt” : filter= gt {host:port}/data-services/v1beta1/issues?filter= gt “lt” : filter= lt {host:port}/data-services/v1beta1/issues?filter= lt “in” : filter= in {host:port}/data-services/v1beta1/issues?filter= in “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= eq and lt
  • 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
sort
string

resource property to sort, with an order appended Order may only be either “asc” (ascending) or “desc” (descending)

Example: sort=/issues?sort=id desc
select
string

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.

Responses
200

Issues list

400

Bad/Malformed request

401

Unauthenticated request

403

Unauthorized request

404

The filter attribute's value does not exist

405

Method not supported

422

Unprocessable input request

500

Internal server error

503

Service unavailable

Request samples 
Response samples 
application/json
{
  • "count": 0,
  • "offset": 0,
  • "total": 0,
  • "items": [
    ]
}