Analyze the Raw List of Remote Display Latency Reports with REST API

REMOTE_DISPLAY_LATENCY_RAW returns average values of remote display latency for each device type in each location. For example, you can check the latency in one or several locations, for one or all device types.

Each entry from REMOTE_DISPLAY_LATENCY_RAW represents the latency of a specific device in a specific location, including data center location, device name and type, timeframe, remote display protocol and so on.


About how long Aternity keeps this data (retention period) and how far back you can go, as well as about how many hours or days of data Aternity returns by default read here.


To visually present this data on the dashboard, go to the Aternity console Main Menu > Analyze > Remote Display Latency (Advanced). (learn more).

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 Aternity REST API, enter the base URL from Aternity > User icon > REST API Access, followed by the name of the API into a browser, Excel or PowerBI (learn more). For VIEWING, use <base_url>/latest/API_NAME; for INTEGRATIONS, use <base_url>/<version number>/API_NAME (for example, <base_url>/v1/API_NAME, or <base_url>/v1.0/API_NAME, or <base_url>/v2/API_NAME, or <base_url>/v2.0/API_NAME).

Get the latest REST API version for analyzing in the external app

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


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

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 ''), or several parameter-value pairs each separated by an ampersand (&), like .../API_NAME?$format=xml&$top=5.

Query Options Description

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


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


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


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

Also, use $top to filter the returned data and to return only the first N entries.

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


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 for filtering with any of the following operators:

Query Operators Description

Equal to

For example, COL4 eq 'val4'


Not equal to

For example, COL4 ne 'val4'


Greater than

For example, COL4 gt 'val4'


Greater than or equal

For example, COL4 ge 'val4'


Less than

For example, COL4 lt 'val4'


Less than or equal

For example, COL4 le 'val4'


Logical and

For example, COL1 eq 'value1' and COL2 ne 'value2'


Logical or

For example, COL1 eq 'value1' or COL2 ne 'value2'


Logical negation

Create conditions for filtering with any of the following functions:

Query Functions Description

For example, $filter=startswith(account_name,'Aternity')


For example, $filter=endswith(account_name,'Aternity')



For example, $filter=contains(account_name,'Aternity')


Instead of using AND, OR:

$filter=device_name eq ‘adam_covert_wks’ or device_name eq ‘adam_covert_vdi’ or device_name eq ‘adam_covert_tablet’

You can now use:


Read carefully specific instructions for writing this function:
  • In must be followed directly by the opening parenthesis (no space allowed)

  • The first parameter is the field name (case insensitive)

  • The function requires at least two parameters, the field name and at least one field value

  • The rest of the parameters are the optional values that the field can have (i.e. the values we want to filter in) also case insensitive

  • Values are separated by comma and no spaces allowed

  • The last value must be followed by the closing parenthesis (no space allowed)

  • In() can be combined with any other filter using AND or OR

  • There can be more than one in() function in a filter. For example, $filter=in(location,’loc1’,’loc2’) or in(subnet,’sub1’sub2’). Another example, $filter=in(location,’loc1’,’loc2’) and in(subnet,’sub1’sub2’)


Limit the timeframe of a query.

If no relative_time filter is used to set a specific timeframe, Aternity will return the default last N days worth of data. Default values vary for different APIs. Learn here about specific REST API.

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'))

$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.




You can view personally identifiable information (PII) in RAW, HOURLY and DAILY aggregations of Aternity's REST APIs, but there is no PII in the DAILY_ANONYMIZED APIs (learn more). There is no PII in any API which has data for longer than three months.

You can access data using this API (retention) going back up to 7 days. If you do not add a relative_time filter, by default Aternity returns data for the past 1 day.

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




Account_ID,Account_Name,Business_Location,Calendar_Date,Calendar_Month,Calendar_Week,Client_Device_Name,Client_Device_Type,Client_Device_Subnet,Corp_Channel,Corp_Line_Of_Business,Corp_Market,Corp_Store_ID,Corp_Store_Type,Custom_Attribute (1-6 or 1-9),Custom_Pilot_Group,Custom_User_Attribute1-9,Data_Center_Business_Location,Device_Active_Subnet,Device_Connection_Location,Device_CPU_Cores,Device_CPU_Frequency,Device_CPU_Generation,Device_CPU_Model,Device_CPU_Type,Device_Days_From_Last_Boot,Device_Domain,Device_Image_Build_Number,Device_IP_Address,Device_Manufacturer,Device_Memory,Device_Model,Device_Name,Device_Network_Type,Device_Power_Plan,Device_Subnet,Device_Type,Location_City,Location_Country,Location_On_Site,Location_On_VPN,Location_Region,Location_State,MS_Office_License_Type,MS_Office_Version,OS_Architecture,OS_BITLocker_Protection_Status,OS_Disk_Type,OS_Family,OS_Free_Disk_Space,OS_Name,OS_Version,Remote_Display_Protocol,SLA_Status,Timeframe,User_Connection_Location,User_Department,User_Domain,User_Email_Address,User_Full_Name,User_Office,User_Role,User_Title,Username,Virtualization,Wifi_BSSID,Wifi_Channel,Wifi_SSID,