Account_ID
(For users who have access to more than one account, like service providers)
Filter by the company ID to retrieve results from just one account. For example,
.../aternity.odata/API_NAME?$filter=(ACCOUNT_ID eq
'12345')
.
Account_Name
(For users who have access to more than one account, like service providers)
Displays the company name. You can filter the output by the
ACCOUNT_ID
, not ACCOUNT_NAME
. For example,
.../aternity.odata/API_NAME?$filter=(ACCOUNT_ID eq
'12345')
.
Action_Count
Displays the number of actions reflected in each result row.
Action_Execution_Status
Displays the status of actions.
There are several
statuses:
- Completed: The
remediation process is completed. Refer to the
Action States to learn how
it was completed.
- In progress: The
remediation process is running. Refer to the
Action States to learn in
what stage it is now.
Action_Last_Update_Timestamp
Displays the date and time when an action got its current state during its life
cycle.
Action_Name
Displays the name of an executed remediation action.
Action_Output_Message
Displays a message that scripts return (if scripts are defined to return messages).
For example, if the script failed for some reason, you can examine the Action
Output Message to get more information about the reason of failure.
Action_Run_Reference_ID
Displays a unique reference number of each action run, which can be used to uniquely
identify each action run.
Action_Script_Duration
Measures the time to complete a script execution.
Action_State
Displays the state of actions.
Completed actions
can be of different states:
- Completed successfully:
The remediation has been successfully
completed.
- User declined: The user
does not want to run this operation on the device
and declined the action.
- Failed: The script failed
for some reason. Examine the Action Output
Message to get more information.
-
Rejected by Agent’s signing policy: The action was rejected
because of the signing policy predefined for the
Aternity
Agent.
- Action Expired: The action did not eventually run during the
allowed time period (set in the action
definition). It can be that the user was logged
out, or did not confirm the notification message,
or the Agent for End User Devices was not connected.
- Action timeout: If the script is running more than five
minutes, the Agent for End User Devices stops the action.
Actions that are in
progress have different states:
- Triggered: The remedy
action has been sent to Windows monitored
device.
- Agent waiting for user
login: A user is not logged in and
cannot confirm the action execution.
- Notification issued to user: A user is logged in and the
Agent for End User Devices is waiting for user confirmation to start a
remediation.
- Action running: A user
confirmed running a remedy script on the device
and the script is running on the Windows monitored
device.
Action_Trigger_Timestamp
Displays the time when the remedy action is being sent to Windows monitored
device.
Action_Trigger_Type
Displays the type of triggers for remediation actions. It can be manual when
executed by an IT person or automatic when executed by an SDA rule.
Action_Triggerred_By
Displays by whom the remediation action was executed. It can be Aternity user
name who executed an action or SDA rule name that triggered an
automatic action.
Action_Triggerred_By_Reference_ID
Displays the reference ID of the service desk alert (SDA) that automatically
triggered the remediation action run. This allows to see if eventually the SDA was
pushed to some external system and if remediation succeeded and the issue is
resolved.
Action_Run_Volume
Displays the total number of remediation actions during the aggregation time of this
API.
Active_Subnet
Displays one of the subnet values on this device whose network adapter is active,
operational and non-virtual.
Activity_Additional_Info1, Activity_Additional_Info2
Activity_Backend_Time
(For managed
applications only) Displays the backend time for a single activity. The backend time for a single request-response pair is from
the last send to its first response minus the round trip time. If the activity calls a server more than once, or
several servers, the reported time is the combination (union) of all the
individual times together. If the target server calls other back-end
servers, Aternity's
backend time is the total (union) of all network times and server times of
all back end servers in that chain, ending when the activity's target server
sends its response to the client. For more server-side visibility, view the
transaction
details in Aternity APM (previously AppInternals).
Definition of backend time in a client-server application
Activity_Backend_Time_Avg
(For managed
applications only) Displays the backend time for a single activity, or
the average backend time if this entry covers several activities. The time displays with the unit of
milliseconds.
The backend time for a single request-response pair is from
the last send to its first response minus the round trip time. If the activity calls a server more than once, or
several servers, the reported time is the combination (union) of all the
individual times together. If the target server calls other back-end
servers, Aternity's
backend time is the total (union) of all network times and server times of
all back end servers in that chain, ending when the activity's target server
sends its response to the client. For more server-side visibility, view the
transaction
details in Aternity APM (previously AppInternals).
Definition of backend time in a client-server application
Activity_Client_Time
(For managed
applications only) Displays the client time for a single activity
in milliseconds. Client time is the time used by the device itself as part
of an activity to
process data before sending its first message request to the server and after
the last message response arrives back from the server.
The Agent for End User Devices calculates the client time as
the total activity response
time minus the infra time.
Client time is the time on the device side to process data as part of the
activity response
Activity_Client_Time_Avg
(For managed
applications only) Displays, in milliseconds, the client
time for a single activity,
or the average client time if this entry covers several activities.
Client time is when the device processes data before or after sending to the
server
Activity_Client_Time_Avg
(For managed
applications only) Displays average the client
time in milliseconds for all the activities
covered in this entry.
Client time is the time used by the device itself as part
of an activity to
process data before sending its first message request to the server and after
the last message response arrives back from the server.
The Agent for End User Devices calculates the client time as
the total activity response
time minus the infra time.
Client time is the time on the device side to process data as part of the
activity response
Activity_Detection_Status
Activity_Diverse_Value_1 - 3
Diverse_Value fields display extra custom contextual data reported as part
of your custom activity which Aternity cannot
aggregate, like an error message. Contextual attributes are descriptive properties of a
measurement or activity, like a username, window title or application
name.
Activity_ID
Displays the unique identifier of the monitored
activity. Crucial for activities with identical names that refer to
different applications, like Save in MS Word and MS Excel.
Activity_Is_Predefined
Displays whether the activity is predefined (True) or not
(False). Aternity comes with default
predefined activities out of the box, for popular business
applications. For example, there are many predefined activities for the
applications in Microsoft Office, like Outlook's open mail or send
mail. There are predefined activities for Acrobat Reader, Microsoft
Office 2007, 2010, 2013 and 2016 (Outlook, Word, PowerPoint, Excel, all in
English), Microsoft Skype for Business and Citrix WorxMail for mobile
devices.
Activity_Measurement_Type
Activity_Name
Displays the name of the monitored
activity within the application as it appears in the dashboards.
An activity is
a user action which you monitor for performance, like a mouse click or a key
press, to measure the time until the app's GUI responds, known as the activity
response time.
In Aternity, you can compare
response times in any app across the enterprise, and troubleshoot
performance by seeing when they perform slower. For example, you can
monitor the launch of an application, or the time it takes for an application to
respond to a menu choice.
Activity_Network_Time
Displays the network
time of this activity in milliseconds. Network time is the total time (union) taken for all
messages to cross the network in either direction, between the client and the
target server, while performing an activity. This does NOT include the time used for
processing the request on the server (backend time).
The network time is calculated as the infra time minus the
backend time.
Network time is the time for all messages to cross the network and back as
part of an activity response
Activity_Network_Time_Avg
(For managed
applications only) Displays, in milliseconds, the network
time for a single activity,
or the average network time if this entry covers several activities.
Network time is the time for all messages to cross the network and back as
part of an activity response
Activity_Page_Title
Displays the activity's Title field, if the activity reported
this as one of its contextual fields.
For example, if an activity measures the time taken for a window to open, the
Title would refer to window or page title.
Activity_Remote_Display_Latency_Avg
The remote display latency is the average time taken for
the round trip of a network data packet to travel between the front line
user and a virtual server (both ways).
Practically, it is the time between performing an action
in a virtual session on the front line user's machine, then sending that
action to the virtual desktop server (VDI) or virtual application server,
and then viewing that action back on the front line terminal again. This
does NOT measure the time for the application to respond.
For example, if a user types the character
'g' in a text editor which runs on a virtual
application server, when the remote session sends this action to the virtual
server, the remote display latency is the lag time between typing
'g' to seeing the 'g' on the
screen.
Remote display latency is the time in both directions from the front line
user to the virtual server
Activity_Response_Time
Activity_Response_Time_Avg
Activity_Score
Activity_Volume
(For managed
applications only) Displays the number of times someone performed this activity during the timeframe, thereby adding weight to the impact of
this problem. If the same user performs the same activity twice,
it counts as two.
Age_In_Days
Displays the time elapsed since the timestamp of the collection of the data in
days.
Age_In_Hours
Displays the time elapsed since the timestamp of the collection of the data in
hours.
Age_In_Minutes
Displays the time elapsed since the timestamp of the collection of the data in
minutes.
Agent_Current_Status
(Windows, Macs) Displays the reporting status of the Agent for End User Devices:
-
The status of a device is
Reporting
if
Aternity is actively
receiving monitoring data from that device.
-
(For Windows and Macs) The status of a
device is Disconnected
if Aternity has not received
monitoring data for more than five minutes from this device, but it has received
data within the last 7 days.
This could be caused by powering off the
device (may be company policy to switch off every night), or it may not have a
license to report to
Aternity, or it could
point to a problem with the device, like no network connection.
When the Agent is
disconnected, it locally stores up to 50 minutes
of retention data in offline mode, and then sends it when it renews its
connection.
-
(For Windows and Macs) The status of a device is
Stopped
if its Agent behaves unusually (like high
CPU or memory usage), and therefore it automatically shuts down. Contact
Customer Services.
(For mobile
devices) Aternity Mobile reports a
status Stopped when it does not collect performance data,
but can still receive commands from the Aggregation Server.
-
(For monitored mobile apps only) The status of a device is
Not Reporting
if Aternity has not received
monitoring data from this mobile device for at least 10 minutes.
This could happen if the device is shut
down, or the device has no network data connection, or the mobile app is running
in the background or is not running at all.
Agent_Version
Displays the version of
the Agent for End User Devices on the device.
Application
The name of the application, as
specified in the Description field of
the executable file's properties.
Tip
Web Browsing is an umbrella term for
all web browsing in your organization on sites which are not
white listed or where the web server is not
inside the enterprise network or VPN (intranet). To white
list a site, add it as a managed application.
An internet browser is
both a container of web applications and a desktop application in its own right. You can
monitor a browser's performance by viewing its launch times
and recent crashes in Monitor Application,
and its memory and CPU consumption in the Analyze Process Resources
dashboard.
Application_Active_Time_Total
The active time of an application is the time when it is running, in the
foreground, and the user is actively interacting with it (NOT waiting for it
while it is busy trying to respond). It is calculated as the usage time minus the
wait time.
Application_Crashes_Total
Displays the number of crashes during the time slot of this entry:
-
(Windows desktop apps) Aternity registers a Windows
app crash when the Event Log issues event ID 1000 (a process or DLL ends
unexpectedly), event ID 1001 (.NET process ends unexpectedly), event ID
1002 (a user stops a Not Responding process), or event ID
1026 (.NET runtime error).
(Mac desktop apps) Aternity
reports a native Mac app crashing only if it registers the crash in the MacOS
system log.
-
(Mobile
apps) Aternity
reports a crashing monitored
mobile app if it experiences an unhandled exception, or if the
operating system (iOS or Android) tells it to abruptly stop (abort
signal).
For every mobile app crash, Aternity collects the exception
code and type of exception, the app's stack trace, and a summary of the crash
information. It also collects any breadcrumbs leading up to
the crash. You can download the memory dump file if needed.
-
(Web
applications) Displays the number of browser crashes.
Application_Hang_Time_Total
Hang time measures the time when an application is listed as
Not responding in the Windows Task Manager while it
is in the foreground (in use). This measurement is used to calculate the wait time of an
application, and the overall UXI.
The time displays with the unit of
milliseconds.
Application_ID
Displays the internal
ID of the mobile app which Aternity monitors, like com.company.mymobileapp. Depending
on the OS, this is known as the Application ID,
Bundle Identifier, Package ID or
Package Name.
Application_Identifier
(Discovered applications only) Displays the
process name (exe) for desktop apps, the base URL for web apps, or the
package name / bundle identifier for mobile apps.
Select or filter with this column to view one
app whose public ('pretty') app name may have several variants, like
notepad++.exe whose app name can be Notepad++, Notepad++ :
a free (GNU) source code editor, Notepad++ (32-bit x86), or
Notepad++ (64-bit x64). Alternatively, some apps may have one public
('pretty') name with several process names, like localized versions of an app.
In those cases, filter by this column to split the app's measurements into each
flavor.
Application_Last_Used_Date
Displays the date when the application was used for the last time.
Application_Minutes_Running_Total
Displays the number of minutes that the process of this application has been running
on this device.
Application_Name
The name of the application, as
specified in the Description field of
the executable file's properties.
Tip
Web Browsing is an umbrella term for
all web browsing in your organization on sites which are not
white listed or where the web server is not
inside the enterprise network or VPN (intranet). To white
list a site, add it as a managed application.
An internet browser is
both a container of web applications and a desktop application in its own right. You can
monitor a browser's performance by viewing its launch times
and recent crashes in Monitor Application,
and its memory and CPU consumption in the Analyze Process Resources
dashboard.
Application_Type
Displays the type of an application:
Application_Version
Displays the
version number for this application, which the Agent for End User Devices retrieves from the executable's Properties >
Details.
Application_Usage_Time_Total
The usage time of an application is the
total time it is running, in the foreground, and being used. This includes
the wait time, the
time a user spends waiting for the application to respond.
For web applications, the usage time is when both the
browser window and the application's tab are in the
foreground.
The time displays with the unit of milliseconds.
Definition of usage time
Applications_Usage_Type
Displays how the application was used: locally or virtually (for desktop devices) or
from a mobile device.
Application_UXI_Avg
The User Experience Index (UXI) is a value
(0-5) which measures the overall performance and health of applications,
based on the number of crashes per hour out of the total usage time, the
percentage hang
time out of the total usage time, and the percentage wait time out of
the total usage time. For web applications, it also uses the percentage of web page
errors out of all page loads, and the average page load
time.
Application_UXI_Weight_Avg
Use this weight to create an average of several measurements of the application's
UXI.
To combine several readings into a single value, you
cannot take a simple average, since this is a cumulative measurement, not a spot
measurement, hence each reading relies on and contains those which came
beforehand. Therefore each measurement needs its own relative weight, which you
can use to include it as part of an overall average. Use this weight value (from
Aternity's
proprietary algorithm) to recreate the weighted average displayed in Aternity's
dashboards:
Sum(UXI * UXI_Weight) / Sum(UXI_Weight)
Application_Wait_Time_Total
The wait time of a Windows application is defined as
the time users spend waiting for the application to respond when it is actively
running and in use (part of the usage time).
The time displays with the unit of
milliseconds.
The total wait time is calculated as the
time covered by the following components (which may overlap): the hang time when an
application is not responding, or when the mouse pointer has a busy icon
(Windows devices). For web applications, the
wait time is the web page
load time when both the browser window and its tab are in the
foreground.
Definition of wait time on a Windows or web application(For
monitored
mobile apps only) , the wait time covers the following components which may overlap: the launch
time of the app, the time spent waiting for the app to switch from the
background to the foreground, the time required for a web page to load within
an app, and the time the user spends waiting for the app's main thread to
respond.
For Mac apps, wait time is the time during
which the app's main UI thread is not as responsive as it should be (slower
performance).
Action
Displays the action which the user performed, which Aternity
audited.
For the Aternity access audit API, it only logs a successful sign in to Aternity, which it
displays as Login.
For the Aternity dashboard audit API, it logs:
-
Open Dashboard
-
Dashboard Interaction, such as changing a parameter, marking a
selection, or changing a filter.
Audit_Action_Timestamp
Displays the earliest timestamp for all
fields in this entry, in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Average_Response_Time_1d, Average_Response_Time_1h,
Average_Response_Time_5min
Displays (in milliseconds) the average
response time of this activity in the past five minutes, the past hour or the
past 24 hours.
Average_Call_Duration
Displays the average length of calls actively connected during this time slot, in
seconds.
Baseline_Attribute
Displays the selected monitored attribute of the baseline, by which the baseline is
split. By default, it is Location, but it can be updated in the
Monitor Tree. First, the Global baseline is shown,
and below different split attributes. If there are no splits, Aternity displays only
the Global value.
Baseline_Attribute_Value
Displays the value of the attribute by which the baseline is split (for example,
Location can be London and Paris).
Baseline_Calculation_Timestamp
Displays the date and time that the baseline was last calculated or updated.
Baseline_Major_Percentile
Displays the baseline percentile that is defined in the Detection Settings for the
Major baseline. If the baseline detection is not defined,
the value is not displayed.
Baseline_Major_Value
Displays the Major baseline that is calculated. If the
baseline detection is not defined, the value is not displayed.
Baseline_Minor_Percentile
Displays the baseline percentile that is defined in the Detection Settings for the
Minor baseline. If the baseline detection is not defined,
the value is not displayed.
Baseline_Minor_Value
Displays the Minor baseline that is calculated. If the
baseline detection is not defined, the value is not displayed.
Baseline_Quality
Once the minimum number of measurements are available for creation of a baseline, the
baseline is created and gets a quality grade. The quality of the baseline impacts
the quality of detection, since a baseline that has Low quality may create
more false positives than a High quality baseline. A baseline is defined as
Low quality if it has a very high STD and/or was calculated using a low number of
measurements.
Baseline_STD
Displays the standard deviation for the measurements used to create the baseline.
When calculating a specific percentile for detection, a number of STDs are added to
the average to calculate that value.
Baseline_Value
Displays the average of all measurements used for the baseline calculation.
Browser
(For web
applications only) Displays the type of web browser housing the application.
Browser_Version
Displays the version number for this browser, which the Agent for End User Devices retrieves from
the executable's Properties > Details.
Business_Location
(For applications or activities) Displays the name of
the locations where the application is
used.
(For devices) Displays the current
geographic location of the device.
For example, if
some users still complain of poor performance after your
change, you can isolate whether the slow results are
restricted to one location or are spread across your
organization. Use Locations to
compare the performance before and after a change for each
location.
Calendar_Date
Displays the date in ISO 8601 format, always at midnight.
For example, March 20th 2018 appears as
2018-03-20T00:00:00+01:00
, where the
+01:00
is the time zone of the Aternity REST API Server. Add
$select
on this column to display daily aggregations of
measurements which include personally identifiable information.
Calendar_Month
Displays the month of the year for which
the query returns data, in the format yyyy/mm. For example, February 2018
is displayed as 2018/02.
Calendar_Week
Displays the week of the year for which
the query returns data, in the format yyyy Week xx. For example, the
second week of the year 2018 is displayed as 2018 Week 02.
Call_Audio_Capture_Device_Driver
Displays the name of the audio
capture device driver.
Call_Audio_Capture_Device_Name
Displays the name of the audio
capture device.
Call_Audio_Combined_Network_Degradation
Displays the maximum value out
of a given Audio Inbound Network
Degradation and Audio
Outbound Network Degradation.
Call_Audio_Fwd_Err_Correction_Used
Displays
True if Skype dynamically switched on
forward error correction (FEC) in a call, to combat packet loss.
FEC sends extra packets containing redundant information, to
help it complete the audio stream on the other end, hence it
uses more bandwidth.
Call_Audio_Inbound_Bandwidth_Estimate
Displays an estimated bandwidth
for incoming audio data (in bits per second).
Call_Audio_Inbound_Codec_Name
Displays the name of the
codec which Skype used to understand the incoming compressed
sound.
Skype dynamically
chooses the best codec to compress the audio signal, based
on the bandwidth available and ensuring the recipient can
unzip the audio on the other side.
Call_Audio_Inbound_Concealed_Samples_Average
Displays the average percentage
of audio frames with samples generated by packet loss
concealment.
Call_Audio_Inbound_Concealed_Samples_Max
Displays the maximum percentage
of audio frames with samples generated by packet loss
concealment.
Call_Audio_Inbound_Jitter
Displays the differences
(variance) in the delay of incoming audio packets from the other
caller, or (in conference calls) from the Skype server to a
caller, measured in milliseconds.
Wide differences in
delay (above 30ms) means that some packets are much
slower than others, so when they arrive at the other end,
the order of the packets is jumbled, which creates a choppy
or distorted sound. This is usually caused by network
congestion, but you can counter it with a large enough
buffer to re-order the jumbled packets.
Call_Audio_Inbound_Jitter_Average
Displays the average jitter for
the incoming audio data in milliseconds.
Call_Audio_Inbound_Jitter_Max
Displays the maximum jitter for
the incoming audio data in milliseconds.
Call_Audio_Inbound_Media_Bypassed
Displays the
True value if audio data
bypassed the mediation server.
Call_Audio_Inbound_Network_Degradation
Displays the network impact on
incoming audio MOS as estimated by Aternity.
Call_Audio_Inbound_Network_Jitter_Average
Displays the average network
jitter for incoming audio data in milliseconds.
Call_Audio_Inbound_Network_Jitter_Max
Displays the maximum network
jitter for incoming audio data in milliseconds.
Call_Audio_Inbound_Packet_Loss
Displays the percentage
audio network packets in a Skype call which were lost in transit
before reaching the participant. Any value above 5%
affects audio quality significantly.
Call_Audio_Inbound_Packet_Loss_Average
Displays the average packet loss
for the incoming audio data.
Call_Audio_Inbound_Packet_Loss_Max
Displays the maximum packet loss
for the incoming audio data.
Call_Audio_Inbound_Packet_Utilization
Displays the packet count for
incoming audio data.
Call_Audio_Inbound_Round_Trip_Time_Average
Displays the average round trip
time for incoming audio data in milliseconds.
Call_Audio_Inbound_Round_Trip_Time_Max
Displays the maximum round trip
time for incoming audio data in milliseconds.
Call_Audio_Outbound_Codec_Name
Displays the name of the
codec which Skype used to compress the outgoing sound.
Call_Audio_Outbound_Jitter
Displays the differences
(variance) in the delay of outgoing audio packets reaching the
other caller, or (in conference calls) from a caller to the
Skype server, measured in milliseconds.
Wide differences in
delay (above 30ms) means that some packets are much
slower than others, so when they arrive at the other end,
the order of the packets is jumbled, which creates a choppy
or distorted sound. This is usually caused by network
congestion, but you can counter it with a large enough
buffer to re-order the jumbled packets.
Call_Audio_Outbound_Jitter_Average
Displays the average jitter for
the outgoing audio data in milliseconds.
Call_Audio_Outbound_Jitter_Max
Displays the maximum jitter for
the outgoing audio data in milliseconds.
Call_Audio_Outbound_Network_Degradation
Displays the network impact on
outgoing audio MOS as estimated by Aternity.
Call_Audio_Outbound_Packet_Loss
Displays the percentage
of audio network packets in a Skype call which were lost in
transit on its way to the other caller, or (in conference calls)
from a participant to the Skype server. Any value above
5% affects audio quality significantly.
Call_Audio_Outbound_Packet_Loss_Average
Displays the average packet loss
for the outgoing audio data.
Call_Audio_Outbound_Packet_Loss_Max
Displays the maximum packet loss
for the outgoing audio data.
Call_Audio_Outbound_Round_Trip_Time
Displays the time for an audio
packet on a Skype call to reach the destination and come back
again to the caller.
Call_Audio_Render_Device_Driver
Displays the name of the audio
render device driver.
Call_Audio_Render_Device_Name
Displays the name of the audio
render device.
Call_Callee_Device_Type
The device of the
callee (a Microsoft term) is the type of device
used by the other participant in a Skype or Lync
call:
-
PC indicates the other participant
used Skype for Business or Lync running on a Windows
desktop or laptop.
-
Conference Bridge indicates that
this user was in a conference call, where every
participant connects via the bridge. Hence the callee is
the conference bridge.
-
iPhone indicates the other
participant used the mobile iOS version of Skype for
Business or Lync on an iPhone.
-
iPad indicates the other
participant used the tablet iOS version of Skype for
Business or Lync on an iPad.
-
Android indicates the other
participant used the Android version of Skype for
Business or Lync on an Android tablet or phone.
-
Mac indicates the other
participant used the Mac version of Skype for Business
or Lync on a Mac desktop or laptop.
-
Other can refer to a gateway or
mediation server.
Call_Combined_Listening_MOS
Displays the combined MOS for this participant in this Skype call. The Mean Opinion Score (MOS) is Microsoft's quality measurement (0-5)
of a user's experience in a Skype or Lync call. It assesses quality by measuring the
network jitter, background noise, dropped packets, and other factors to score the
user experience for a single device in a single call. Each device in a call has an
inbound MOS and an outbound MOS.
Participants in a call have their own MOS scores and statuses
Call_Connection_Type
Displays the type of calls in
Microsoft Teams: Direct between
two devices, or Conference, where
more than two devices connect to a bridge to participate
in a call. Each connection to a call appears in the
dashboards as a separate entry.
Call_Capture_Device_Model
Displays the name of the capture
device. A capture device is a microphone, either built-in
or standalone, used for collecting audio input to a Skype / Lync call.
Call_Capture_Device_Driver_Ver
Displays the name and
full version of the driver which supports the capture device in a Skype call. A capture device is a microphone, either built-in
or standalone, used for collecting audio input to a Skype / Lync call.
Call_Direction
Displays:
-
Incoming are the people who
answered a Skype or Lync call.
-
Outgoing are the people who dialed
a Skype or Lync call.
For example, if you have a
call center and expect most calls to be incoming, you can
confirm this expectation by monitoring the dominant call
direction.
Call_Duration
Displays the duration of a user's
call or session.
This is NOT the duration of the
entire call (for conference calls, when people can
connect or disconnect at any time, the duration of a
user's call and the duration of the entire call are not
necessarily equal).
Call_End_Reason
Displays the
quality and performance of calls which ended in different
ways:
-
Ended Successfully are for calls
which started and ended normally, with no unexpected
disconnections.
-
Disconnected with Error: A stream is dropped if Microsoft Teams, or Skype for
Business, or Lync ended the call unexpectedly, without the user manually ending
the call. Aternity reports the
failure and its reason.
-
Failed Streams: A stream fails if Skype for Business or Lync could not
successfully establish a connection and start. Aternity reports the failure and
its reason as the SIP code and SIP string.
Call_Error_Code
Displays the
Skype for Business error code for a failed call.
A stream fails if Skype for Business or Lync could not
successfully establish a connection and start. Aternity reports the failure and
its reason as the SIP code and SIP string.
Call_ID
Displays the Call ID from
Microsoft Teams by which users can locate and view a
specific call record (common to all participants of a
unique call).
Call_Inbound_Degradation
Displays the inbound
degradation for this participant of a Skype call. Inbound degradation is the amount of
reduction in the inbound MOS
score which was due to a poor network connection. A high degradation
indicates that the poor network MOS (packet loss, network jitter) played a significant role
in lowering the audio experience.
Call_Inbound_Listening_MOS
Displays the inbound
MOS score for this participant. The inbound MOS (or inbound listening MOS) for someone in a
call is the MOS score
of the incoming audio or video, showing if you clearly hear others in the call
over background noise or a poor connection (inbound network MOS). The inbound MOS of a listener is
the same as the outbound
MOS of the speaker.
For example, if the other person spoke softly, or there
was poor network speeds, or a dog was barking, it would lower the inbound
MOS.
The combined MOS score (and status) for a device is the
LOWER value of the inbound MOS and outbound MOS scores in a call.
Call_Inbound_Network_MOS
Displays the network
MOS score for this participant. The inbound network MOS is part of the overall inbound listening MOS
which focuses on the network connection quality like packet loss and network
jitter.
Call_Media_Audio
Indicates if audio was used in
the call (True). Otherwise it is
False.
Call_Media_Sharing
Indicates if media sharing was
used in the call (screen or application
sharing).
Call_Media_Video
Indicates if video was used in
the call (True). Otherwise it is
False.
Call_Mode
There are two types of calls in Skype for Business or Lync:
Direct between two devices, or
Conference, where more than two devices connect to a
bridge to participate in a call. Each connection to a call appears in the
dashboards as a separate stream.
Call_Network_Connection_Delayed_Audio_Impact
Displays the percentage of the
call where the network delay was significant enough to
impact the ability to have real-time two-way
communication.
Call_Network_Connection_Low_Bandwidth_Audio_Impact
Displays the percentage of the
call where the available bandwidth or bandwidth policy
was low enough to cause poor quality of the audio
sent.
Call_Network_Connection_Received_Audio_Quality_Impact
Displays the percentage of the
call where the network was causing poor quality of the
audio received.
Call_Network_Connection_Sent_Audio_Quality_Impact
Displays the percentage of the
call where the network was causing poor quality of the
audio sent.
Call_Network_Connection_Subnet
Subnet used for the
call.
Call_Network_Connection_Type
Displays the network connection
type, like WiFi, wired, or else.
Call_Network_Connection_WiFi_Signal_Strength
Displays the percent strength of
the WiFi signal which the device receives, which can
impact communication speed.
Call_Render_Device_Model
Displays the the
manufacturer and model name of a participant's audio output
(render) device, and the type of device, like
speakers or headphones.
Call_Render_Device_Driver_Ver
Displays the full
version and manufacturer of the driver which supports the audio
output (render) device.
The render device is a participant's speaker or
headphones which outputs the audio of a Skype / Lync call.
Call_Sipcodeid
Displays the SIP error code
on a failed Skype call. A stream fails if Skype for Business or Lync could not
successfully establish a connection and start. Aternity reports the failure and
its reason as the SIP code and SIP string.
Call_Sipstringid
Displays the SIP error
details on a failed Skype call. A stream fails if Skype for Business or Lync could not
successfully establish a connection and start. Aternity reports the failure and
its reason as the SIP code and SIP string.
Call_Sharing_Inbound_Frame_Rate_Average
Displays
the average frames per second received for a video
stream, computed over the duration of the
session.
Call_Sharing_Inbound_Packet_Utilization
Displays the
packet count for the stream.
Call_Stream_Failed
Displays 1 if the call or stream could not successfully establish a
connection, 0 if it did establish a connection.
A stream fails if Skype for Business or Lync could not
successfully establish a connection and start. Aternity reports the failure and
its reason as the SIP code and SIP string.
Call_Stream_Is_Dropped
Displays whether Skype for Business dropped a call
or stream (1) or did not drop the call (0). A stream is dropped if Microsoft Teams, or Skype for
Business, or Lync ended the call unexpectedly, without the user manually ending
the call. Aternity reports the
failure and its reason.
Call_Stream_Type
There are two types of streams in Skype for Business or Lync:
Audio only or
Audio/Video.
Call_Stream_Volume
Displays the total number of streams performed in Microsoft Teams during the given
time slot. For example, when three people are talking, although it is one distinct
call, but there are three streams, so three records will be saved and calculated as
three separate streams. This API field displays the volume of streams during this
time slot.
Call_Stream_Volumes
Displays the total number of Skype calls during this time slot. For example, when
three people are talking, although it is one distinct call, but there are three
streams, so three records will be saved and calculated as three separate streams.
This API field displays the volume of streams during this time slot.
Call_Time
If users retrieve the raw data, each row displays the length of one specific call.
If users retrieve the aggregated data for many calls:
Displays the
total length of calls actively connected during this time
slot, in seconds.
Note
The call duration is NOT the usage time of Skype/Lync, since you can continue
a call while the application runs in the background, or you
can perform IM chats in the foreground without making a
call.
Call_Unique_Volume
Displays the number of unique calls in MS Teams.
Call_User_Feedback_Rating
Displays the different call
quality feedback ratings that can be provided by a user
at the end of a call.
Call_Username
Displays the name of Microsoft
Teams user logged in to the device.
Call_Video_Capture_Device_Driver
Displays the name of the video
capture device driver.
Call_Video_Capture_Device_Name
Displays the name of the video
capture device.
Call_Video_Inbound_Fec_Packet_Loss_Average
Displays the number of packets
lost for incoming video data after the
Forward Error Correction has
been applied.
Call_Video_Inbound_Frame_Loss_Percentage
Displays the average percentage
of incoming video frames loss.
Call_Video_Inbound_Low_Frame_Rate
Displays the percentage of
incoming video where frame rate is less than 7.5 frames
per second.
Call_Video_Inbound_Low_Processing_Capability
Displays the percentage of the
call that the client has less than 70% of expected video
processing capability.
Call_Video_Inbound_Packet_Loss_Percentage
Displays the percentage of
incoming video packets loss, computed over the duration
of the session.
Call_Video_Inbound_Packet_Utilization
Displays the packet count for
the incoming video data.
Call_Video_Render_Device_Driver
Displays the name of the video
render device driver.
Call_Video_Render_Device_Name
Displays the name of the video
render device.
Call_Volumes
Displays the number of distinct calls (not participants) performed in Skype for
Business.
Change
Displays the description of what was changed by Aternity users.
Change_Additional_Information
Displays the details from an audit log that records an event. It may include
destination and source addresses, a timestamp and user login information.
Change_Timestamp
Display the date and time when the change applied.
Change_Type
Displays the type of changes that were made by Aternity users and
audited.
Client_Device_Name
(For virtual
deployments only) Displays the hostname of a device which is connecting to a VDI
or virtual application server.
Client_Device_Type
(For virtual
deployments only) Displays the type of front line terminal which runs the
virtual session hosted on a virtual server.
If the front line terminal
has an Agent for End User Devices locally installed, it reports the type of device of the terminal. Otherwise, if it
does not have its own Agent, it reports it as a Remote Device.
Component_Name
Displays the name of the system component, as it appears on the System
Health dashboard; for example, Aggregation
Server.
Component_Status
Displays the status of the component as appears on the System
Health dashboard (for example, Free disk space is running
low). Statuses are as follows:
-
-
Green
represents the
Status - Running.
-
Yellow
represents the
Status - Running with
Warnings.
-
Red
represents the
Status - Failed/Not
reporting.
-
Gray
represents the
Status -
Unknown/Starting.
Component_Status_Details
The status details are error messages, warning messages or any other message shown as
tooltips on user interface when you hover the mouse over the
Status for each row.
Component_Uptime_In_Days
Displays the component startup time.
Components_Version
Displays the version of the system component, for example, <REST API build
number>.
Connected_Agents
Displays the number of devices of this Device_Type in this
location where the status of the Agent for End User Devices was
Reporting, Stopped or Not Reporting during the past
seven days.
-
The status of a device is
Reporting
if
Aternity is actively
receiving monitoring data from that device.
-
(For Windows and Macs) The status of a device is
Stopped
if its Agent behaves unusually (like high
CPU or memory usage), and therefore it automatically shuts down. Contact
Customer Services.
(For mobile
devices) Aternity Mobile reports a
status Stopped when it does not collect performance data,
but can still receive commands from the Aggregation Server.
-
(For monitored mobile apps only) The status of a device is
Not Reporting
if Aternity has not received
monitoring data from this mobile device for at least 10 minutes.This could happen if the device is shut
down, or the device has no network data connection, or the mobile app is running
in the background or is not running at all.
Connected_Remote_Devices
Displays the number of devices of this Device_Type in this
location which did not have a locally deployed Agent, and where
the status of that remote Agent was
Reporting.
The status of a device is
Reporting
if
Aternity is actively
receiving monitoring data from that device.
Contextual_01_16_Label
Contextual attributes are descriptive properties of a
measurement or activity, like a username, window title or application
name.
When defining a Custom Data Collector, it is possible to collect up to 16 contextuals
(free text), and label each one with a Title or Name. Custom Data dashboard cannot
present the collected free texts, so they are named
Contextual_01_16_Value. To let users know what each
contextual for, Aternity provides the
labels in additional column (Contextual_01_16_Label).
Contextual_01_16_Value
Contextual attributes are descriptive properties of a
measurement or activity, like a username, window title or application
name.
When defining a Custom Data Collector, it is possible to collect up to 16 contextuals
(free text), and label each one with a Title or Name. Custom Data dashboard cannot
present the collected free texts, so they are named
Contextual_01_16_Value. To let users know what each
contextual for, Aternity provides the
labels in additional column (Contextual_01_16_Label).
Corp_Channel
Only displays if you defined a custom attribute
using this predefined name.
A custom attribute is a
property of a device, location or user that you define, which Aternity does not normally detect.
You can use a custom attribute to easily group together the items which share
this property, to monitor their performance.
For example, you can configure Aternity to report if a device has
disk encryption, to compare the performance of encrypted versus regular
devices.
Use this name for an attribute
which differentiates a device, user or location along internal
business units or areas of the company like retail outlet
or customer service center.
Corp_Line_Of_Business
Use this name for an attribute which
displays the type of business associated with this device, like
life insurance, auto insurance, or
finance.
Only displays if you defined a custom attribute
using this predefined name.
Corp_Market
Only displays if you defined a custom attribute
using this predefined name.
Use this
name for an attribute which displays the target market
or business unit of a location, or a user or device in
that area of the company.
Corp_Store_ID
Displays your organization's internal
code that identifies each retail store.
Only displays if you defined a custom attribute
using this predefined name.
Corp_Store_Type
Displays the type of store, for
example, branch, mall, or
superstore.
Only displays if you defined a custom attribute
using this predefined name.
Critical_Status_Count_1h, Critical_Status_Count_1d,
Critical_Status_Count_5min
Display the number of times someone performed this activity
whose status was critical,
when you gather the performance data from the past five minutes, the past hour
or the past 24 hours.
Custom_Attribute_1 - 9
Custom Attribute 1
through 6 are placeholder custom attributes which you can optionally
define.
Only displays if you defined a custom attribute
using this predefined name.
Custom_Pilot_Group
Displays the pilot group assigned to this device. A pilot
group is a custom set of users or devices which undergo a change, like
migrating to Windows 10, or updating the type of hard disk to SSD.
Dashboard_Name
Displays the name of the dashboard, for example, EnterpriseSummary or
DeviceDetails.
Object_Name
Displays the name of the application, activity, user, or device which the Aternity user selected
to drill
down to this dashboard. When auditing the dashboards which you visit,
Aternity also
notes if you arrived at this dashboard after drilling down on an object in another
dashboard.
Object_Type
Displays whether the Aternity user drilled
down to this dashboard by selecting an application, activity, user, or device. This
forms part of the audit of dashboard use.
Data_Center_Business_Location
Data Center Locations in Aternity lists the locations of any virtual
application servers (like Citrix XenApp) and VDI hypervisors (like in VMWare
vSphere) which run the application. If the application is deployed both locally
and virtually, one of the locations displays as
Local.
Device_CPU_Cores
(Desktops, laptops and
mobile devices only) Displays the number of CPU cores of the
device.
Device_CPU_Frequency
(Windows, Macs only) Displays the speed of the
CPU processors of the device.
Device_CPU_Generation
(Windows on Intel only) Displays the generation
of the Intel Core micro-architecture. For example
6 represents the 6th generation architecture
processor, also known as Skylake.
Device_CPU_Model
(Windows on Intel only) Displays the model and
speed of the Intel processor, as displayed in the
System control panel. For
example Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
or Intel(R) Xeon(R) CPU E5620 @
2.40GHz.
Device_CPU_Type
(Windows on Intel only) Displays the core type
of the Intel processor, for example i7,
E5, and so on).
Device_Count
Displays the number of devices reflected in each result row.
Device_Days_From_Last_Boot
Displays the number of days
since the last time the device was booted. If you think that
people experience slowdowns because they have not booted in
some time, you can compare their performance with users who
restart their devices frequently.Possible values are any of the following strings:
-
Less than 24 hours
-
24 - 48 hours
-
2 - 7 days
-
7 - 14 days
-
15 - 30 days
-
More than 30 days
Device_Hours_Running_Total
Displays the percentage of an hour between zero and one during which the device
was running. For example, in a given hour slot (o'clock to o'clock), if a device
has been running for 15 minutes of that hour, this value would be 0.25. Another
device which ran for 45 minutes would have a value of 0.75.
If you calculate the average hourly usage of a shared resource for several
devices using weighted averages, you can use this measurement as the weight for
a device. For example, if several devices each run for different proportions of
that hour, to calculate a weighted average, assign a greater weight to the
device which ran for more time in that hour.
Device_ID_Mobile_Or_Mac
For monitored Android apps, the Device
ID is made up of two parts: the first is the WiFi mac address,
and the second is the software-based ANDROID_ID
.
For monitored iOS apps the Device ID
is only unique per vendor ID. If your enterprise uses a
single vendor ID to create several apps, then whenever they are on the same
device, they report the same Device ID. But an app from a
different vendor ID (like Citrix WorxMail) on the same device would report a
different Device ID.
Device_Idle_This_Hour
Displays whether the device
experience any user interaction during this one-hour slot.
Possible values are true or false. Use this to
monitor resource usage when the device is idle (like
automatic backup processes or virus scanning processes which
run when the computer is idle), or to better calculate
performance averages by excluding the time when the device
stands idle. If a user did not perform any interaction with
the device (e.g. mouse click, keyboard press, application
usage) during a one-hour slot, the device’s idle status will
become true. Note that being on a
call via a collaboration tool (e.g. Zoom, Skype) is not
considered a user interaction, so if a user was on a call
for over an hour without any other interaction (e.g. mouse
click, keyboard press, application usage) the hour will be
counted as idle.
Device_Image_Build_Number
Only displays if you defined a custom attribute
using this predefined name.
Use this name for an attribute which
displays the ID of the disk image used when creating this
device's initial setup and configuration.
Device_IP_Address
(Windows, Mac) Displays the device's internal IP address (including IP
v6 if the device runs Agent 10 or later) which it uses to connect to Aternity.
(Mobile devices) Displays the IP of
the WiFi connection if the device is reporting data via
WiFi.
Device_Memory
Displays the size of physical RAM of the device.
Device_Name
Displays the hostname of
the monitored device. View it in the Windows
Control Panel > System > Computer
Name, or on Apple Macs in System
Preferences > Sharing > Computer Name.
Note
In anonymized APIs, this field is empty. However, for virtual servers, it
displays the hostname of the server.
(Mobile) Displays the Device Name field. You can customize the hostname of iOS or Android
devices running your enterprise's app, so device names
appear in the dashboards with a consistent naming policy.
For example, you can dynamically assign the device name
according to the enterprise username of the app.
Device_Manufacturer
Displays the name of
the vendor which created this device, like
Samsung, Apple,
Dell, Lenovo, and so on.
Device_Model
Displays the name and
the model number of the device, like iPhone 6s,
GalaxyTab8, MacBook Pro 12.1,
Dell Latitude D620.
Device_Network_Type
(Devices with Agent 9.x or later) Displays
the type of network connection of the device:
Mobile or
WiFi, and also
LAN (for non-mobile devices
only).
Device_Power_Plan
(Windows only) Displays the
Windows power plan which the device uses, governing the way
the computer consumes power (like display brightness, sleep
and so on). You can see this in Control Panel >
Power Options. The default setting is
Balanced.
Device_Serial_Number
(Starting Agent 12.0.1 and/or Agent for Mac 3.2) Displays the device's serial number for Mac, Windows and
virtual devices.
Device_Subnet
Displays
the device's subnet configuration used to connect to
Aternity (including IP v6 if the device runs Agent 10 or later).
Device_Type
Displays the type of the monitored
device:
-
Desktops are
monitored Windows devices without a fitted battery, or for Macs, any monitored MacBook running
macOS or OS X.
-
Laptops are Windows devices with a battery and a
built-in keyboard (including all Windows hybrid tablet/laptop models), or for
Macs, any monitored laptop running
macOS or OS X.
-
Remote
Devices have applications accessed remotely via an RDP
protocol, for example, with Microsoft's Remote Desktop Connection.
-
Smartphones run
monitored mobile
apps on a small touch screen within a mobile operating system
environment.
-
Tablets have larger
touch screens, and no built-in keyboard, running iOS or Android. If it runs
Windows, it is defined as a tablet if it is a known model of a Windows pure
tablet (like Microsoft Surface models).
-
Virtual App
Servers offer multiple users access to a single instance of
an application, for example, with Citrix XenApp.
-
Virtual
Desktops offer the ability to run an application within a
VDI environment, which is a virtual instance of the entire desktop operating
system (usually Windows).
Enforce_Privacy
Displays whether privacy mode is enabled on the device.
(For all devices except mobile) When True, it encrypts any
attributes which can identify a user, like username,
hostname, IP address, and so on. The default value is
False.
Event_Category
Displays the category of an error (or some other custom data) which you track
using an application event of type Application Error Event.
Event_Details
Displays the details of an error (or some other custom data) which you track
using an application event of type Application Error Event.
Event_Duration
Displays the response time of a non-typical business activity which you measure
with an application event of type Application Usage Duration.
Event_Type
Displays the type of application event:
-
Application Usage Duration is for
measuring the time to complete a non-typical complex business activity,
like one which includes application response times mixed with time
waiting for the user. For example, use this to measure the time required
for a user to identify a customer at the beginning of a call.
-
Application Usage Event is for
counting the times when an event occurred, or when it is not easy to
identify the end event of an activity.
For example, if you want to track the number of
times when people shared their desktop in Skype for Business, track this
as an application usage event, and assign a
Category to different types of usage
events.
-
Application Error Events are for
tracking the occurrence of errors. Each error has a
Category, or type of error, and a
Details field, which contains details of the
event or error.
Health_Event_Category
A system
health event for a device is a significant problem at the level of the operating
system which impacts on the device's overall health, like BSODs or other
system crashes. The categories are:
-
Application
Displays application health events on applications which
have a user interface.
-
Background Process
Displays application health events for programs which run
in the background, without a user interface, like Windows
services.
-
Hardware
Displays hardware health events like memory paging and
hardware failures
-
System
Displays system health events, like system crashes
(BSODs)
There are also sub-categories for each of these categories.
Health_Event_Component
Displays the name of the component which caused this health event. For
example, a battery, a network interface, a disk drive,
printer, a process name and version like AcroRd32.exe
19.10.20069 (or Point of Sale
(com.company.app2 for mobile apps).
Health_Event_Component_and_Version
Displays the name and version number of the application process which caused this
health event. For
example, a battery, a network interface, a disk drive,
printer, a process name and version like AcroRd32.exe
19.10.20069 (or Point of Sale
(com.company.app2 for mobile apps).
Health_Event_Component_Type
Displays the type of component which caused this health event,
like Process for applications, Battery, Application ID (for
mobile apps), Drive, Printer, or Network
Interface.
Health_Event_Component_Version
Displays the version number of the component which caused this health event, like
an app's version number.
Health_Event_Details
Displays
additional information about the component which caused this
health event (for example, the memory type for a
memory allocation failure event, or the DLL version of an
application crash, and so on).
Health_Event_Error
Displays the error message with error code which caused this health event. For
example, c06d007e (Exception).
Health_Event_Exception_Type
Displays the type of the error if the application generated an exception at the
heart of this health event. For example,
NSObjectNotAvailableException.
Health_Event_Last_Timestamp
Displays the latest timestamp value within the hour that the event happened at. If
the same event repeats multiple times within the hour, it is possible to see the
exact range within the hour that the event happened at.
Health_Event_Manufacturer_Date
(For Battery wear health events only) Displays the date of manufacture for
the battery in the device when the battery caused this health event.
Health_Event_Manufacturer_Name
(For Battery wear health events only) Displays the name of the
manufacturer for the battery in the device when the battery caused this health
event.
Health_Event_Memory_Consumed
(Mobile app crashes only) Displays the number of gigabytes of RAM in use at the
time of the app crash.
Health_Event_Memory_Type
Displays whether the memory allocation error happened with Paged which
swaps in and out of physical memory, or Nonpaged which always sits in
physical memory:
-
Paged: Windows event
ID 2020 has the description The server was unable to
allocate from the system paged pool because the pool was
empty.
For details and a
solution, search this error ID in Microsoft's support
site.
-
NonPaged: Windows
event ID 2019 is caused by a memory leak. It has the
description The server was unable to allocate from the
system non-paged pool because the pool was empty.
For details and a
solution, search this error ID in Microsoft's support
site.
Health_Event_Memory_Utilization
(Mobile app crashes only) Displays the percentage of RAM in use at the time of
the app crash.
Health_Event_Name
Displays the name of the health event, like Battery wear, Unexpected
shutdown, Low disk space and so on.
Health_Event_Severity
Displays the severity (Level) which Windows allocates for this health
event: Minor, Major, Critical.
Health_Event_Stack
For every mobile app crash, Aternity collects the exception
code and type of exception, the app's stack trace, and a summary of the crash
information. It also collects any breadcrumbs leading up to
the crash. You can download the memory dump file if needed.
Health_Event_Status
(S.M.A.R.T hard disk health events only) Displays the low level status of the
disk, like OK, Degraded, Starting, Stopping or
Pred Fail if the disk is functioning but predicting a likely failure
soon.
Health_Event_Stop_Event_Info
(System crash or BSOD health events only which generated a memory dump) Displays the event, which contains Microsoft's stop
error codes ('bug check
codes').Aternity
analyzes the memory dump for stop error codes and event details.
Health_Event_Sub_Category
Under the main
categories of health events:
Application,
Background Process,
Hardware and
System, there are sub-categories
like Windows Background Process, MobileApp,
DotNet, Network, Battery and so
on.
Health_Event_Sub_Component
Displays the name of the part of the application responsible for the health
event, like the DLL filename which caused the health event.
Health_Event_Sub_Component_And_Version
Displays the name and version of the part of the application responsible for the
health event, like the DLL filename and version number which caused the health
event.
Health_Event_Sub_Component_Type
Displays the type of the part of the application responsible for the health
event, like DLL or Update or Module Info.
Health_Event_Sub_Component_Version
Displays the version number of the part of the application responsible for the
health event, like the version number of the DLL file which caused the health
event.
Health_Event_Volume
Displays the number of times this health event occurred in the time slot of this
entry.
HRC_CPU_Util
(Windows, Mac and
mobile, except Android 8 and later) Displays the percentage
CPU utilization of the core with the greatest usage at a
given time. For example, if the device has four CPU
cores, where one is at 80%, one is at 60% and the others
are idle, it will display a value of 80%.
HRC_CPU_Util_Avg
Displays the average percent CPU usage by a device over the aggregation period,
calculated from data that Aternity aggregates
every two minutes.
HRC_Disk_IO_Read_Rate_Avg
Displays the average rate at which the device reads from the hard disk, in kilobytes
per second ,
calculated from data that Aternity aggregates
every two minutes.
HRC_Disk_IO_Write_Rate_Avg
Displays the average rate at which the device writes to the hard disk, in kilobytes
per second,
calculated from data that Aternity aggregates
every two minutes.
HRC_Disk_Queue_Length_Max
Displays the maximum number of waiting I/O requests to read or write to the hard disk
or a logical disk at a given time.
HRC_Disk_IO_Read_Rate
Displays the rate at which
the device reads from the hard disk in MB per second at any
given time.
For example, if a virus
scanner slows performance by issuing many disk read
requests, reschedule to off-peak times. Alternatively, if
the read rate falls to almost zero, the hard disk may be
failing, or its connection to the computer may be
unreliable.
HRC_Disk_IO_Write_Rate
DIsplays the rate at
which the device writes to the hard disk in MB per second at
any given time.
For example, a movie
editor can perform large disk writes, slowing down the
device's performance. Alternatively, if the write rate falls
to almost zero, the hard disk may be failing, or its
connection to the computer may be unreliable.
HRC_Disk_Queue_Length
(Windows only) Displays the number of
waiting I/O requests to read or write to the hard disk
or a logical disk at a given time during the activity.
A consistent queue for
the disk indicates a bottleneck in hard disk access, which
significantly impacts on system performance, either due to
excess system demands on the disk, or it can be a hardware
disk problem. To check if the problem is hardware, view if
the speed (rate of reads and writes to the disk) is
low
HRC_Mobile_Battery_Level_Max
The maximum battery charge percentage at a given time.
HRC_Mobile_Battery_Level_Min
The minimum battery charge percentage at a given time.
HRC_Network_IO_Read_Rate
Displays the data
downloads of this device in MB per second at any given
time.
For example, if its
throughput or usage of bandwidth is low, and the user
complains of slow network connections, consider checking the
NIC hardware.
HRC_Network_IO_Write_Rate
Displays the data
uploads from this device in MB per second at any given
time during the activity.
For example, if its
throughput or usage of bandwidth is low, and the user
complains of slow network connections, consider checking the
NIC hardware.
HRC_Physical_Memory_Util
(Windows, Macs,
mobile) Displays the percentage usage of the device's physical
RAM memory at a given time during the activity.
HRC_Physical_Memory_Util_Avg
(Windows, Macs,
mobile) Displays the percentage usage of the device's physical
RAM memory at a given time,
calculated from data that Aternity aggregates
every two minutes.
HRC_Virtual_Memory_Util
(Windows only)
Displays the current usage of a device's virtual memory as a
percentage of the device's total virtual memory (physical
RAM plus hard disk allocation for memory page faults) at a
given time during the activity.
HRC_Virtual_Memory_Util_Avg
(Windows only)
Displays the current usage of a device's virtual memory as a
percentage of the device's total virtual memory (physical
RAM plus hard disk allocation for memory page faults) at a
given time,
calculated from data that Aternity aggregates
every two minutes.
Incident_Close_Timestamp
Displays the time when
Aternity automatically closed this incident. When you configure an
incident, you determine the conditions required to
automatically open it, and then when the performance
statuses improve, Aternity can automatically close it. This field is blank for
incidents which are still open.
It displays this in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Incident_Creation_Timestamp
Displays
the date and time when Aternity automatically opened this incident. It displays this in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Incident_ID
Displays the ID of the incident. Use the ID
to quickly locate and follow up on an existing incident by
searching for it in the ID search field a
the top right hand side of the Incident
List dashboard.
Incident_Last_Update_Timestamp
Displays the last date and time when Aternity updated
the details about this incident in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
..
Incident_Live_Impact
Displays the status assigned to this
incident (and its color) which reflects its overall impact.
Aternity assigns an incident's status by collating all the statuses of this activity from devices in the
group into a single incident status.
For example, you can configure
an incident to become Critical when
an activity's status is red in 40% of the monitored devices
in a group.
Incident_Live_Impacted_Users
View the total
number of users (total, not peak) whose devices reported a
major or critical status on this incident's activity while this incident was
active.
Incident_Peak_Impacted_Users
Displays the peak number of
devices which simultaneously reported this problem, at
any point in time from the moment Aternity opened this incident. As each device reports that it
actively suffers from this problem, the number of
devices which simultaneously suffer from this issue
varies over time.
Incident_State
Displays the current state of
the incident. Possible values are:
-
Active indicates the incident is
live, and devices are still suffering from poor response
times in this activity.
-
Closed indicates the devices are
no longer reporting a problem with this activity, and
therefore Aternity closed the incident.
Incident_Peak_Impact_Timestamp
Displays the time and date when this incident had the most users impacted.
It displays this in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Installed_Sw_Change_Timestamp
(For Agents 9.2.3 and later) Displays the time of the last software change. (For
Agents earlier than Agent 9.2.3) If the change happened before you deployed the
Agent, the time stamp displays the time when you deployed that Agent.
Installed_Sw_Change_Type
Displays the types of changes, whether the software was
installed, uninstalled or updated.
Installed_Sw_Count
Displays the number of different software names reflected in each result
row.
Installed_Sw_Installation_Volume
Displays the total number of changes reflected in each result row.
Installed_Sw_Last_Change_Timestamp
Displays the time of the last software change. (Until
Agent 9.2.3
only) If the change took place before you deployed the Agent, it displays the
time when you deployed that Agent.
Installed_Sw_Name
Displays the name of the software which is set up on this device.
Installed_Sw_Related_To
Displays the parent software package related to this setup. For example, if your
query returns a security update for Microsoft Outlook 2010, this column could
display Microsoft Office Professional Plus 2010.
Installed_Sw_Scope
Displays whether the software is set up for all users of this device or a specific
user.
Installed_Sw_Type
(From Agent 9.2.3) Displays the type of software item on this device. It
displays all the device's software items which were set up
for all users, but
does NOT include Universal Windows Platform (UWP)
applications (learn
more).
-
Application displays applications
that you can remove in the Windows Uninstall
or change a program Control Panel, and
system components that do not appear there, such as
Configuration Manager Client.
The Agent takes this list from the Windows Registry under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall,
returning all of the programs that have a value for
DisplayName.
-
OS Update displays Windows
updates, such as patches, hotfixes and service packs. It
does not display OS upgrades, such as Windows 7 to
Windows 10.
The Agent takes this list from WMI (Windows Management
Instrumentation).
Installed_Sw_Vendor
Displays the name of the company that produced the software that is present on this
device.
Installed_Sw_Version
Displays the version of the software that is present on this device.
Installed_Sw_Version_Before_Change
Displays the version of the installed software before the change. Relevant only in
cases where the change type is Updated.
Installed_Sw_Version_Count
Displays the number of different software versions reflected in each result row.
Is_Device_Used_Remotely
Allows a performance optimized solution to distinguish between situations when users
use devices locally as opposed to when they are logged in to a remote device
(whether it is a Virtual application sever, VDI or remote physical device).
This attribute makes your life easier without any need to compare a Client device
name to a Serving device name.
Last_Reported_Date
Displays the last date and time when Aternity received this
data in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
License_Event
Displays Aternity's response to the request for license units. The possible
choices are: Approved or Rejected.
License_Event_Reason
Displays the reason
for the rejection of a license request. The choices
are:
-
no_more_licenses
indicates
that Aternity already reached its full quota of (all types of)
license units. Contact Customer Services to purchase more licenses.
-
type_limit
indicates
that you reached the maximum limit on the number of
units allowed for this type of device. To resolve,
either change the limits for this type of device, or
purchase new units.
-
rollout_limit
indicates that you have reached the temporary limit
of your gradual rollout of license units. Contact
Aternity SaaS Administration to increase the rollout to allow further
allocation of units.
-
session_limit
indicates that Aternity already assigned the maximum number of virtual
sessions for that server. By default you can have up
to 50 simultaneous monitored sessions on a single
virtual application server.
License_Last_Event_Timestamp
Displays the time and date
when the last licensing-related event took place for this
user or device.
License_Owner
Displays the username
(virtual session), hostname (computer) or device ID (mobile) which requested the license
units.
Location_City
Location_Country
Location_On_Site
(Windows only) Displays
true when the device can identify and
connect to the Microsoft Active Directory site (either directly
or via VPN).
Location_On_VPN
(For all devices except
mobile and Macs) Displays true when the
device is connected to the corporate network through VPN.
Location_Region
You can optionally define a region in Aternity to group together several
locations under a
single label, like the geographical region of EMEA, North America
or even Southern Europe, South-Western US any other grouping you
choose.
Location_State
Displays the
geographical state of the current location of the devices (or area, if state is
not applicable).
Major_Status_Count_1h,
Major_Status_Count_1d, Major_Status_Count_5min
Displays the number of times someone
performed this activity whose status
was major, when you gather the performance data
from the past five minutes, the past hour or the past 24
hours..
Manual_Major_Threshold
Displays the major static thresholds as
defined in the Activity Detection settings.
Manual_Minor_Threshold
Displays the minor static thresholds as
defined in the Activity Detection settings.
Max_Disk_Queue_Length
Displays the maximum number of waiting I/O requests to read or write to the hard disk
or a logical disk during the aggregation period.
Max_Timestamp
Displays the last timestamp for all
fields in this entry, in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Measurement_01_12_Label
When defining a Custom Data Collector, it is possible to collect up to 12 measurements,
and label each one with a Title or Name. Custom Data dashboard cannot present the
label of the collected field, so they are named
Measurement_01_12_AVG. To let users know what each
Measurement for, Aternity provides the
labels in additional column (Measurement_01_12_Label).
Measurement_01_12_AVG
When defining a Custom Data Collector, it is possible to collect up to 12 measurements,
and label each one with a Title or Name. Custom Data dashboard cannot present the
label of the collected field, so they are named
Measurement_01_12_AVG. To let users know what each
Measurement for, Aternity provides the
labels in additional column (Measurement_01_12_Label).
Measurement_Duration_Avg
Displays the length of the boot time. The type of boot time is in the Type field.
Measurement_Start_Timestamp
An activity's measurement time is the time stamp when
the Agent for End User Devices on the device noted
the occurrence of the activity. The time stamp is translated to the time zone of
the Aggregation Server.
Measurement_Type
Displays the type of boot, whose length is in the Duration
field. The choices are:
-
User Logon
: User logon measures a part
of the boot time, starting when you press OK at the
Windows sign in screen and ending when the Windows desktop Start button
appears.
The Agent queries
Windows Shell-Core (NOT the Event Log) for the
Explorer_StartMenu_Ready event to mark the end of
this time.
-
Total Boot Duration
: The total boot
time on a Windows device starts from the time the Windows logo appears until
the desktop appears and all components are loaded.
Agent queries
Windows Event Log (ID 100) for the BootTime parameter,
calculated as the sum of main path boot and post boot times, located in the
Diagnostics > Performance > Windows section of
the log.
-
Machine Boot
: Machine boot is part
of a device's boot time, starting a fraction of a second after the Windows
logo appears, and ending with the Windows sign in screen.
Agent queries
Windows Kernel-PnP (NOT the Event Log) for the BootStart >
Start event to mark the start of this time, and ends when
the Windows sign in screen appears (or the automatic sign in process
starts).
Tip
In some cases with a very fast boot, or when Windows bypasses the full boot
process, the Agent only reports
the user logon time.
Boot time definitions
Minor_Status_Count_1h,
Minor_Status_Count_1d, Minor_Status_Count_5min
Displays the number of times someone
performed this activity whose status
was minor, when you gather the performance data
from the past five minutes, the past hour or the past 24
hours.
Mobile_SDK_Version
Displays the version of the embedded Aternity Mobile in the
app, which is responsible for collecting and reporting performance measurements
to Aternity.
Mobile_Carrier
(Mobile devices only) Displays the name of the
cellular carrier to which the device is connected.
Monitor_Category
A folder where the Custom Data Collector resides. When collecting many custom data,
it helps to unify it. For example, you can create a category Device
Statistics.
Monitor_Name
The name of the monitor. For example, you can name the monitor Disk
Statistics or being more specific Disk Free
Space.
MS_Office_License_Type
(Windows only) Displays the
type of license for Microsoft Office, if installed.
Typically it is either Subscription
for Office 365, or Volume License for
more traditional license purchases.
MS_Office_Version
Displays the high level
version of Microsoft Office, like MS Office 2016 or
MS Office 2013.
MS_Stability_Index
Displays the Microsoft Stability index for a Windows device. The stability index (used to be reliability
value) is a Windows score (from 1 to 10) of a PC's
overall stability (search in Windows for the Windows Reliability
Monitor). As the number and severity of errors increases, it
lowers the stability index. Aternity displays the average for
the previous day, or, if unavailable, it shows the most recent daily average.
The server versions of Windows do not have this measurement, and therefore would
not report it to Aternity.
Network_Incoming_Traffic_Total, Network_Outgoing_Traffic_Total
Aternity reports the
total volume of network traffic in KB in both directions while an
application performs an activity.
Network_Read_Avg
Displays the average data download speed for this device, in kilobytes per second ,
calculated from data that Aternity aggregates
every two minutes.
For example, if its
throughput or usage of bandwidth is low, and the user
complains of slow network connections, consider checking the
NIC hardware.
Network_RTT_Avg
Displays the average round trip time (RTT) for this device. The time displays with the unit of
milliseconds.
A single message and its acknowledgment, before any server processing
Network_Time_Avg
Displays the network
time of this activity, or if the API delivers aggregated results, it
displays the average network time for this activity over the aggregation period. The time displays with the unit of
milliseconds.
Network time is the total time (union) taken for all
messages to cross the network in either direction, between the client and the
target server, while performing an activity. This does NOT include the time used for
processing the request on the server (backend time).
The network time is calculated as the infra time minus the
backend time.
Network time is the time for all messages to cross the network and back as
part of an activity response
Network_Write_Avg
Displays the average data upload speed for this device, in kilobytes per second,
calculated from data that Aternity aggregates
every two minutes.
Normal_Status_Count_1h,
Normal_Status_Count_1d, Normal_Status_Count_5min
OS_Architecture
Displays whether the operating
system of the monitored device is 32-bit or 64-bit.
OS_BITLocker_Protection_Status
(Windows only) Displays the status
of the BitLocker Protection for operating system drive in
Windows.
OS_Free_Disk_Space
Displays the
amount (GB) of free space on the device's system disk which
contains the operating system installation. The free disk space measurements are grouped as follows:
- Up to 0.5 GB
- 0.5GB - 1 GB
- 1 GB - 2 GB
- 2 GB - 3 GB
- 3 GB - 4 GB
- 4 GB - 5 GB
- 5 GB - 10 GB
- 10 GB - 20 GB
- 20 GB – 50 GB
- 50 GB - 100 GB
- 100 GB - 200 GB
- 200 GB - 500 GB
- 500 GB and above
OS_Disk_Type
(Windows only, Agent 9.0.3 or later) Displays the type of hard disk containing
the operating system. Possible values are:
-
HDD for a traditional spinning
hard disk drive
-
SSD for a solid state drive
-
Virtual if this is not a physical
device.
OS_Family
Displays the broad
category of the operating system. Use this to differentiate
between different major operating system groups.
For example, it displays all
releases of Microsoft Windows as MS Windows, all
releases of Windows Server as MS Windows Server or
all releases of iOS as iOS.
OS_Name
Displays the generic name and version of the operating
system (like MS Windows 10, MS Windows Server
2008 R2, MacOS 10.3, iOS 10 or
Android 6).
For example, it displays
Windows 10 Pro and Windows 10 Enterprise
all as MS Windows 10
OS_Version
Displays the full name,
the exact version number, and the service pack version of
the operating system. In Windows 10, it includes the release
ID (like Microsoft Windows 10 Enterprise 1507). Use
this to differentiate between details of the same operating
system. For example, it lists MS Windows Server 2008 R2
Enterprise SP 1.0 separately from MS Windows
Server 2008 R2 Enterprise SP 2.0.
Call_Outbound_Listening_MOS
Displays Skype's outbound MOS score for this participant of the call. The outbound MOS for someone in a call is the MOS score of your
outgoing audio or video, showing if others clearly hear you in the call over
background noise or a slow network (inbound network MOS).
For example, if you have a poor microphone or speak
quietly far away from the mic, it would reduce your outbound MOS score for that
call.
Page_Load_Backend_Time_Avg
Page_Load_DNS_Time
Displays the time required to perform a domain lookup with DNS, as part of the total
load time of a
web page.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Web page load time
Page_Load_DNS_Time_Avg
Displays the average time required to
perform domain lookups with DNS, as part of the total load time of a web page.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Web page load time
Page_Load_Client_Time_Avg
(For web
applications only) Displays the average time spent for client side processing during the load time of
a web page.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Client time is the time used by the device itself as part
of an activity to
process data before sending its first message request to the server and after
the last message response arrives back from the server.
Web page load time
Page_Load_HTTP_Status_Code
Displays the HTTP status code returned by a web page, such as 403 Forbidden or
404 Not Found.
Page_Load_Network_Time_Avg
(For web
applications only) Displays the average network time portion of the load time of a web page.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Network time is the total time (union) taken for all
messages to cross the network in either direction, between the client and the
target server, while performing an activity. This does NOT include the time used for
processing the request on the server (backend time).
Web page load time
Page_Load_Time
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Web page load time
Page_Load_Time_Avg
(For web
applications only) Displays the average load time of a web
page for this application.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Web page load time
Page_Load_Processing_Time
Displays the average time that the
status of the DOM (document object model) is Loading
until it changes to Complete, as part of the total load time of a web page. During this time, the
browser may issue further requests and receive responses.
Web page load time
Page_Load_Processing_Time_Avg
Displays the average time that the
status of the DOM (document object model) is Loading
until it changes to Complete, as part of the total load time of a web page. During this time, the
browser may issue further requests and receive responses.
Web page load time
Page_Load_Redirect_Time
Displays the average time to
redirect to a different URL, if the page requires redirection,
as part of the total load time of a web page. This includes a DNS request
for the original URL and retrieval of the alternate URL.
Web page load time
Page_Load_Redirect_Time_Avg
Displays the average time to
redirect to a different URL, if the page requires redirection,
as part of the total load time of a web page. This includes a DNS request
for the original URL and retrieval of the alternate URL.
Web page load time
Page_Load_Request_Time
Displays the average time between
the first request to the server, and the first response from the
server, as part of the total load time of a web page.
Web page load time
Page_Load_Request_Time_Avg
Displays the average time between
the first request to the server, and the first response from the
server, as part of the total load time of a web page.
Web page load time
Page_Load_Response_Time
Displays the average time between
the first response from the server to the last response from the
cache or the server, as part of the total load time of a web page.
Web page load time
Page_Load_Response_Time_Avg
Displays the average time between
the first response from the server to the last response from the
cache or the server, as part of the total load time of a web page.
Web page load time
Page_Load_TCP_Connect_Time
Displays the average time required to
establish the regular or secured TCP connection, as part of the
total load time of a web page.
Web page load time
Page_Load_TCP_Connect_Time_Avg
Displays the average time required to
establish the regular or secured TCP connection, as part of the
total load time of a web page.
Web page load time
Page_Load_Volume
(For web
applications only) Displays the number of times a web page load took place during this time
slot.
The web page load time is the time required for a web page
to load and finish rendering in a browser, from sending a URL request to when
the page's events finish loading and it has a status of Completed. This
measurement does NOT include the time to load additional page elements which
occur after the main page has loaded, such as iframes that are embedded separate
web pages, AJAX calls after the page is complete, or bookmarks with
# in the URL). It does include AJAX calls that the
page makes before it is complete.
Web page load time
Performance_Index
The performance index is a value (0-5) which measures an
application's responsiveness. If users must wait frequently or for long periods
for an application to respond, its performance index is lower. It is calculated
from the usage time and
wait time.
Definition of performance index
Performance_Weight
Use this weight to create an average of several measurements of the application's
performance
index.
To combine several readings into a single value, you
cannot take a simple average, since this is a cumulative measurement, not a spot
measurement, hence each reading relies on and contains those which came
beforehand. Therefore each measurement needs its own relative weight, which you
can use to include it as part of an overall average. Use this weight value (from
Aternity's
proprietary algorithm) to recreate the weighted average displayed in Aternity's
dashboards:
Sum(Performance_Index * Performance_Weight) /
Sum(Performance_Weight)
PRC_CPU_Util
View the percentage CPU utilization of
this Windows process while it performs an activity, measured as a percentage of
the total power of all CPU cores available.
During an activity, if an application uses
resources (x% CPU or RAM), or sends x MB of network traffic, it is not the same
as saying that it is because of the activity. They happen at the same
time, so they are correlated (see Correlation vs. Causation). However, you can be
reasonably confident that these device measurements occurred because of the
activity.
PRC_CPU_Util_Avg
Displays the average CPU
usage (in percent) of this managed application during the timeframe, which is part of the application's
process resource consumption (PRC).
PRC_CPU_Util_Max
Displays the peak CPU
usage (in percent) of this managed application during the timeframe, which is part of the application's
process resource consumption (PRC).
PRC_GDI_Objects_Total
Displays a measure of the device's graphics resource usage in Windows. The
Agent
collects this value only if manually configured in your deployment.
PRC_Not_Responding_Errors_Total
The Aternity
Agent checks the
application's process resource consumption (PRC) of the
managed
application a few times a minute to validate it's responsiveness. Then,
the Agent reports
the total number of times it checked the PRC (as
PRC_Sampling_Count_Total value), and how many of those returned with an
error (PRC_Not_Responding_Errors_Total value). This indicates there is a
message loop inside a long running process which does not respond in a timely manner
or completely got stuck). Divide PRC_Not_Responding_Errors_Total by
PRC_Sampling_Count_Total to get an appropriate process resource
unavailability metric.
PRC_Sampling_Count_Total
The Aternity
Agent checks the
application's process resource consumption (PRC) of the
managed
application a few times a minute to validate it's responsiveness. Then,
the Agent reports
the total number of times it checked the PRC (as
PRC_Sampling_Count_Total value), and how many of those returned with an
error (PRC_Not_Responding_Errors_Total value). This indicates there is a
message loop inside a long running process which does not respond in a timely manner
or completely got stuck). Divide PRC_Not_Responding_Errors_Total by
PRC_Sampling_Count_Total to get an appropriate process resource
unavailability metric.
PRC_Physical_Memory_Consumed
View the amount of working set memory for
this Windows process while it performs an activity.
REST API returns memory usage values in bytes.
If the activity always coincides with a
spike in memory consumption, this is probably the cause of slow
performance.
During an activity, if an application uses
resources (x% CPU or RAM), or sends x MB of network traffic, it is not the same
as saying that it is because of the activity. They happen at the same
time, so they are correlated (see Correlation vs. Causation). However, you can be
reasonably confident that these device measurements occurred because of the
activity.
PRC_Physical_Memory_Util_Avg
Displays the average
usage of a managed application's physical memory (known as
the total working set) in megabytes during the timeframe, which is part of the PRC.
PRC_Physical_Memory_Util_Max
Displays the peak
usage of a managed application's physical memory (known as
the total working set) in megabytes during the timeframe, which is part of the PRC.
PRC_User_Objects_Total
Displays a measure of the device's usage of resources assigned to window
management. The Agent collects
this value only if manually configured in your deployment.
PRC_Virtual_Memory_Consumed
View the amount of reserved memory
(commit size) for this Windows process, while it performs an activity.
REST API returns memory usage values in bytes.
If the activity always coincides with a
spike in memory consumption, this is probably the cause of slow
performance.
During an activity, if an application uses
resources (x% CPU or RAM), or sends x MB of network traffic, it is not the same
as saying that it is because of the activity. They happen at the same
time, so they are correlated (see Correlation vs. Causation). However, you can be
reasonably confident that these device measurements occurred because of the
activity.
PRC_Virtual_Memory_Util_Avg
Displays the average
usage of a managed application's reserved memory (commit
size) in megabytes during the timeframe, which is part of the application's
process resource consumption (PRC).
PRC_Virtual_Memory_Util_Max
Displays the peak
usage of a managed application's reserved memory (commit
size) in megabytes during the timeframe, which is part of the application's
process resource consumption (PRC).
Process_Name
Displays the name of the monitored
Windows process of the managed application, as displayed in the Windows
Task Manager.
Reliability_Grade
Reporting_Agents
Displays the number of devices of this Device_Type
in this location where the status of the Agent for End User Devices was
Reporting during the past seven days.
The status of a device is
Reporting
if
Aternity is actively
receiving monitoring data from that device.
Row_Creation_Time
Displays the time when a row was added to the database.
Score_1d, Score_1h, Score_5min
SD_Alert_Identifier
Displays the important details of the service desk alert, like the app name which
crashed, or the disk name which issued an error. Filter or select this column
name to view all errors associated with a particular app or disk. A service desk alert (SDA) indicates that the same health event occurred
several times on the same device within a certain time. Aternity sends SDAs to draw
attention to devices which suffer repeated application errors, system crashes or
hardware issues.
SD_Alert_Last_Event_Details
Displays the full details of the last occurrence of this health event. For app
crashes, this includes the app name, its process name (or base URL),, and any
error codes. For disk failures, it includes the disk name and the error codes
associated with this health event.
A service desk alert (SDA) indicates that the same health event occurred
several times on the same device within a certain time. Aternity sends SDAs to draw
attention to devices which suffer repeated application errors, system crashes or
hardware issues.
SD_Alert_Last_Event_Timestamp
Displays the time and date of the last health event which triggered this service
desk alert.
A service desk alert (SDA) indicates that the same health event occurred
several times on the same device within a certain time. Aternity sends SDAs to draw
attention to devices which suffer repeated application errors, system crashes or
hardware issues.
SD_Alert_Reference_ID
Displays a unique reference number to each service desk alert that can be used to
uniquely identify each alert, for example in the ticketing system.
A service desk alert (SDA) indicates that the same health event occurred
several times on the same device within a certain time. Aternity sends SDAs to draw
attention to devices which suffer repeated application errors, system crashes or
hardware issues.
SD_Alert_Rule_Name
Displays the name of this service desk alert.
A service desk alert (SDA) indicates that the same health event occurred
several times on the same device within a certain time. Aternity sends SDAs to draw
attention to devices which suffer repeated application errors, system crashes or
hardware issues. The types of alerts are:
-
HD Failure
Windows event ID 52 occurs
with an imminent failure of the hard disk.
Back up your data
immediately, then use a scanning tool to detect problems.
For example, if a disk is too hot, switch off the PC and
disconnect the power of that hard disk until you replace
it.
-
Application Crash (after hang)
(Windows) Event ID
1002 occurs when a user manually forced an application's
process to close after it stopped responding. (Mac) Aternity uses the system log to determine when a user has manually
forced an application's process to close after it stopped
responding.
To resolve, note any
common actions leading to the hang, then consult the app
vendor's support site.
-
Battery Wear
(Windows laptops
only) Aternity checks if the battery capacity drops below a threshold
(default is 50%), compared with the vendor's factory
settings. This indicates that a full battery charge drains
much faster than it should.
To resolve, replace
the battery.
-
HD Bad Blocks
Windows event ID 7 occurs
with a corrupted block of data on the hard disk. If many bad
sectors develop, the drive may fail and needs
attention.
Replace a physically
damaged disk immediately. For 'soft' or logical bad sectors,
you can use Windows Disk Check.
-
Low Disk Space
Aternity creates this event if the device's system disk has less
than 5% free space and less than 500MB available, which
limits the size of virtual memory. Event will be created
when both conditions are met. To resolve, free some disk space (empty trash, remove
unused apps) or increase its capacity.
-
Overheat Related Shutdown
Windows event ID 86 occurs
when the device shuts down due to overheating (critical
thermal event).
It indicates a hardware
problem, like a dusty CPU, broken fan or obstructed air
vent.
Turn off your computer,
clean the heat sinks, and make sure that air circulates
properly.
-
System Crash
(Windows) Aternity reports a system crash when Windows created a memory dump
file after a BSOD. Aternity analyzes the Windows dump and extracts data. (Macs) Aternity reports a system crash when it detected a kernel panic
from the macOS system logs.
To troubleshoot, view the
details of the event and research further on the name of the
process or module and its error codes.
Server_Hostname
Displays the actual
hostname of the server (NOT its DNS alias), when an
application on the device contacts a server. For example, on
a device using Outlook 365, the hostname might be
outlook-emeacenter.office365.com while its DNS
name is shortened to outlook.office365.com. This is a clearer
definition to replace Target
Server.
If you contact more
than one server during an activity, it reports the server
whose total backend time was longest during that
activity.
Server_IP
Displays the IP address of
the server, when an application on the device contacts a
server. For example, on a device using Outlook, it displays
the IP address of the Exchange server. This is a clearer
definition to replace Target
Server.
If you contact more
than one server during an activity, it reports the server
whose total backend time was longest during that
activity.
Server_Name
Displays the DNS alias
of the hostname of the server (not the computer's actual
hostname), when an application on the device contacts a
server. For example, on a device using Outlook 365, the DNS
name might be outlook.office365.com while its full
hostname might be
outlook-emeacenter.office365.com. This is a clearer
definition to replace Target
Server.
If you contact more
than one server during an activity, it reports the server
whose total backend time was longest during that
activity.
Session_Key
Displays the internal ID of this connection to Aternity. Every
time you open a new browser tab, it has a unique session ID. Use this to
determine the number of times a person opened a different session to Aternity.
Session_Type
Displays the type of request that a user signed in for:
-
UI when using Aternity web
application.
-
aodata when using REST API queries.
-
onapp when using WAC.
SLA_Status
Time_Last_Reporting
Displays the last date and time when Aternity received this
data in ISO 8601 format. For example, July 20th 2016 at
03:15am in the UTC time zone appears as 2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
. If the device was idle, or
the user did not run any discovered or managed apps, this field remains empty.
Timeframe
In REST API, timeframe displays the earliest timestamp for all
fields in this entry, in ISO 8601 format. For example, July 20th 2016
at 03:15am in the UTC time zone appears as
2016-07-20T03:15:00Z
or
2016-07-20T03:15:00+00:00
.
Add this as a filter when you need to separate out an aggregated measurement into the
individual measurements with their time stamps. Alternatively, you can limit the scope of a query to the period between two
static times, by creating a filter of a timeframe greater than or equal to
(ge
) the start time and less than or equal to
(le
) the end time.
For example: $filter=((TIMEFRAME gt
2018-06-09T16:00:00+01:00 and TIMEFRAME lt 2018-06-11T18:00:00+01:00) or
(TIMEFRAME gt 2018-06-13T16:00:00+01:00 and TIMEFRAME lt
2018-06-15T18:00:00+01:00))
Tip
Alternatively you can filter for relative_time()
(recommended)
which returns the dynamic most recent data, to refresh your query without
re-entering a new static time. For example,
$filter=relative_time(yesterday)
.
Note
Timeframe
in Aternity
dashboards has a different definition (learn
more).
Total_Event_Volume
The total number of times a certain event occurs in the specified timeframe,
calculated as summary.
Unique_Hourly_Events
When the same event occurs multiple
times within one hour, it is counted just once for that hour.
For example, if a background process crashes, cannot start and
keeps crashing and starting again, creating hundreds of crash events within one hour, Aternity counts them as one Unique Hourly Event
every hour. Displaying hundreds of rows of the duplicated
crash event causes dashboard usability problems, makes it
difficult to find a really important information, and
reduces dashboard value and user experience. The
Unique Hourly Events value minimizes
duplications and repetitive information and enhances dashboard
value and user experience.
User_Connection_Location
Displays the reported location of the monitored device. The possible values are:
Remote (VPN On), Remote (VPN Off),
Remote (Non-Corporate VPN),
In-Office.
User connection location and device connection location may be different when working
remotely.
User_Department
Displays the name of the department to which the user or the device
belongs.
(Windows) Agent sends LDAP
queries to the Active Directory (AD) to find information about the connected
domain controller, then extracts the user's > Properties >
Department
.
(Mobile) Mobile apps can set this manually in the Aternity Mobile SDK.
User_Domain
Displays the LDAP domain name
for the user who is logged in to the device.
User_Email_Address
(Windows only) Displays the email address associated with
the current logged in user.
User_Name
Displays the Aternity username of the person associated with the audited action inside Aternity. This is NOT
the operating system's username.
Username
Displays the username signed
in to the device's operating system.
User_Office
(For all devices except mobile) Displays the office where the current user logged in to
this device.
For example, if a user
based in the Houston office is currently visiting the
Chicago office, the Office is
Houston, while the
Location would be
Chicago.
User_Role
Displays user role descriptions customized by your
organization, for example, Floor Sales, or Phone
Support.
Only displays if you defined a custom attribute
using this predefined name.
User_Title
Displays the job title of
the current user logged in to this device. In Windows, this
is the same as the AD Title. This is sourced as follows:
-
(Windows) Agent sends LDAP
queries to the Active Directory (AD) to find information about the connected
domain controller, then extracts the user's > Properties >
> Organization > Title
(Title
).
-
(Mobile) Displays only if
you
configured it in the Aternity advanced
settings.
-
(Macs) Displays only if you
manually mapped this
device to a department.
User_Type
Displays the type of user who signed in to Aternity:
-
LocalUser refers to a user which you defined locally inside Aternity.
-
SamlUser refers to a user who signed in via SSO with the SAML
protocol.
-
LDAPUser refers to a user defined and managed in your Microsoft Active
Directory.
-
SamlGroupUser refers to users who signed in via SSO with the SAML
protocol and were not explicitly defined but get their roles from an SSO
Group they belong to.
Users_Count_Last_7_Days
Displays the number of unique users who performed this activity
during the past seven days.
Virtual_App_Server_Edition
Displays the edition name of the product running virtual app server, like
XenApp Advanced or XenApp Platinum.
Virtual App
Servers offer multiple users access to a single instance of
an application, for example, with Citrix XenApp.
Virtual_App_Server_Farm
If the virtual app server belongs to a set of load balanced servers, known as a
farm, it displays the name of the farm.
Virtual App
Servers offer multiple users access to a single instance of
an application, for example, with Citrix XenApp.
Virtual_App_Server_Version
Displays the release or version number of the product running the virtual app
server.
Virtual App
Servers offer multiple users access to a single instance of
an application, for example, with Citrix XenApp.
Virtual_App_Server_Zone
Displays the name of zone within
the farm, where all servers
use the same data collector, which acts as their load
balancer.
Virtual App
Servers offer multiple users access to a single instance of
an application, for example, with Citrix XenApp.
Virtual_Server_Name
(When virtual sessions request license units from Aternity) If a
CItrix XenApp session is requesting license units, it displays the hostname of
the XenApp server. For VDI sessions, it displays the hostname of the virtual
desktop monitored in this session.
Virtualization
Displays 1 if this took place on a VDI virtual machine or on a virtual
application server. Displays 0 if it took place on a physical
device.
Volume (Activities)
Displays the number of times this activity was performed by this username on this
device during the aggregation time of this API.
Volume_1d, Volume_1h, Volume_5min
Volume_5min, Volume_1h, and
Volume_1d
display the total number of times someone
performed this activity in the past five minutes, the past hour or the
past 24 hours.
Volume_Last_7_Days
Displays the number of times anyone performed this activity
during the past seven days.
Wifi_BSSID
(From Agent 9.2 or Agent for Mac 2.3) Displays the
ID (MAC address) of the wireless access point, which the
device currently uses to connect to a WiFi
network.
Wifi_Channel
(From Agent 9.2 or Agent for Mac 2.3) Displays the channel number which your device uses to
connect to the WiFi router. Use this to ensure channels
do not overlap one another in the same physical space.
Your network performance significantly drops if a nearby
WiFi router uses an overlapping channel with the same
network speed.
WiFi_Hours_Connected_Total
Displays the total proportion of this hourly slot (between zero and one) when the
device was connected to the network via WiFi.
Wifi_Noise_Level_Avg, Wifi_Noise_Level_Max, Wifi_Noise_Level_Min
(Macs only) Displays
the background noise level of the WiFi connection for this
device, measured in decibels. High noise levels lower the
quality of a connection (signal to noise ratio), which slows
the effective speed of that connection, which in turn lowers
an application's performance.
Wifi_Signal_Strength_Avg, Wifi_Signal_Strength_Max,
Wifi_Signal_Strength_Min
(Windows
Agent 9.2 or later, Macs and mobile devices) Displays the
percent strength of the WiFi signal which the device
receives, which can impact communication speed. For more
details, hover your mouse over the graph in the
dashboard to see the name of the WiFi network connection
(SSID), the wireless network card MAC address (BSSID),
and the WiFi channel.
Wifi_SNR_Avg, Wifi_SNR_Max, Wifi_SNR_Min
(Macs only) Displays the WiFi
signal-to-noise ratio (SNR), which is the strength of the data
measured in decibels minus the background noise. Low SNR impacts
significantly on network performance. Higher speed connections
require a higher SNR. For example, at 54 Mbps you need an SNR of
at least 25 decibels.
Wifi_SSID
(From Agent 9.2, or Agent for Mac 2.0 and mobile) Displays the name of the WiFi network where the device
currently connects.
Wifi_Transmission_Speed_Avg, Wifi_Transmission_Speed_Max,
Wifi_Transmission_Speed_Min
(Macs and in Windows
from Agent 9.2) Displays the potential speed (bandwidth) of the WiFi
connection at that moment, in megabits per second (Mbps).
Lower WiFi bandwidth can be due to poor signal strength or
overlapping channels, which slows the network time. In Windows, see the potential
speed in the Control Panel > Network and Sharing
> Adapter Settings > Status of the WiFi
connection. In Macs, view it in About This Mac >
System Report > Network > Wi-Fi.
WiFi network speed on Windows and Macs