Analyze the Incidents Opened in Aternity with REST API (version 1.0)

Use INCIDENTS to view the live list of incidents which Aternity automatically opened for widespread slow performance of an activity. An incident is a call to action about many users suffering poor performance on one activity in an application, indicating it is a widespread problem.

For example, you can view all the activities which have open incidents for a given application, or all the activities whose incidents currently impact more than five users across the enterprise.

Each entry from INCIDENTS returns a single incident with its details like its whether or not it is open (INCIDENT_STATE), its status (INCIDENT_LIVE_IMPACT), and the number of users impacted.

Note

You can access data using this API (retention) going back up to 400 days. With each day that passes, Aternity stores another day of this data.If you do not add a relative_time filter, by default it returns data for the past five days.

Before You Begin

To send a REST API query in Excel, PowerBI or a browser, enter the URL of the REST API, your Aternity username (must have the OData REST API role) and its password. You can find this by selecting User icon > REST API Access. SSO users must generate (once) and use a special password, as Aternity's REST API does not authenticate with your enterprise's identity provider.

To view an Aternity REST API, enter the base URL from User icon > REST API Access, followed by the name of the API: <base_url>/API_NAME into a browser, Excel or PowerBI (learn more). :

Tip

Wherever possible, use $select and $filter to narrow your query, to avoid receiving an error like Returned data is too large. Learn more.

Examples

To access this API from a browser, Excel or Power BI (learn more), enter <base_url>/INCIDENTS.

To view the names of activities in MyApplication which have incidents which are currently open now (status which is Active), enter:

.../INCIDENTS?$select=activity&$filter=(INCIDENT_STATE eq 'Active') and (APPLICATION eq 'MyApplication')

To view the names of applications and their activities which have incidents which currently impact more than five users, enter:

.../INCIDENTS?$select=activity,application&$filter=Incident_Live_Impacted_Users gt 5

Supported Parameters

You can view the data by entering the URL into Excel, into a browser, or into or any OData compatible application such as Power BI.

You can add parameters to the URL to filter the returned data, by adding a question mark (?) followed by a parameter and value, such as .../API_NAME?$filter=(USERNAME eq 'jsmith@company.com'), or several parameter-value pairs each separated by an ampersand (&), like .../API_NAME?$format=xml&$top=5.

Parameter Description
$select=

Use $select to return only specific columns (attributes), to make queries more efficient: ...API_NAME?$select=COL1,COL2,COL3

$filter=

Use $filter to insert conditions that narrow down the data, to return only entries where those conditions are true..

To limit the timeframe of a query, add $filter=relative_time() like, .../API_NAME?$filter=relative_time(last_x_hours) or (last_x_days). Learn more.

Create conditions with operators: and, or, eq (equals) gt (greater than), ge (greater than or equal), lt (less than), le (less than or equal), ge (greater than or equal to), ne (not equal to), le (less than or equal to), not and contains. Use operators with parentheses to group conditions logically: .../API_NAME?$filter=(COLUMN1 eq 'value1' or COL2 neq 'val2') and (COL3 gt number) and not (COL4 eq 'val4' or contains(COL5,'val5'))

$format=

Use $format to force the returned data to be either in XML or JSON format. This is only useful for testing the raw data in a web browser. For example: .../API_NAME?$format=xml

$orderby=

Use $orderby to sort the returned data according to the value you choose. For example, .../API_NAME?$orderby=LOCATION

$top=

Use $top (lower case only) when you are initially testing the response of the API by returning the first few entries.

For example, to return the first five entries (not sorted), use: ...API_NAME?$top=5

$search is NOT supported.

Do not use $search in Aternity's REST APIs.

If you use $select to display only specific columns, it makes the query faster by grouping all rows with identical attribute values into a single row with aggregated measurements. For example, if you use $select to return only the RAM size and CPU usage, if 50 devices have the same attribute of 16GB RAM, it condenses them into a single row and outputs their CPU usage as a single weighted average measurement.

Tip

Wherever possible, use $select and $filter to narrow your query, to avoid receiving an error like Returned data is too large. Learn more.

Output

Each entry from INCIDENTS returns a single incident with its details like its whether or not it is open (INCIDENT_STATE), its status (INCIDENT_LIVE_IMPACT), and the number of users impacted. If you use $select to display only specific columns, it makes the query faster by grouping all rows with identical attribute values into a single row with aggregated measurements.

You can access data using this API (retention) going back up to 400 days. With each day that passes, Aternity stores another day of this data.If you do not add a relative_time filter, by default it returns data for the past five days.

The API returns two types of columns: Attributes (or dimensions) which are the properties of an entry, and Measurements which are the dynamic measured values. A single API row can display either a single measurement, or a weighted average of several entries grouped together. If you use $select to display several attributes, and all those attributes are identical, it groups them into a single entry.

Type Returned columns

Measurements

Incident_Live_Impacted_Users,Incident_Peak_Impacted_Users

Attributes

Account_ID,Account_Name,Activity,Application,Incident_Close_Time,Incident_Creation_Time,Incident_ID,Incident_Last_Update_Time,Incident_Live_Impact,Incident_State,Incident_Worst_Impact_Time