Main Devices page
Selecting any device will open the Device Details view.
You can use Search Devices to filter the table:
- Fqdn contains <search text>
- Fqdn begins with <search text>
The Filters bar appears at the top of most of the pages in Experience. You can expand and collapse the bar.
Each section in the Filters bar allows a user to quickly and easily filter based on different categories. When a filter is set, it applies to all the tiles on the page, and is also applied to other pages when they are viewed.
On the Software page, there is also a filter setting to select the Last x Days, where x is 90 (default), 60, 30, or 7 days. The Last x Days filter is applied to all pages in the same way as other filters, although it can be selected only on the Software page.
On the Stability, Responsiveness, Performance, and Sentiment pages there is also a Break Down By selector that reconfigures the charts to show the data divided up into the selected category.
On the Overview, Categories, Devices, and Software pages there is no option for Break Down By.
On the Users and Surveys pages the Filters bar is not available.
For more information about filters, please refer to Filters.
Device Details view
This data is the last collected data only. There is no ability to look at the history information in this view.
Notice the lines in red with an exclamation point, this is how the scores that have a Very Poor Grading show in some tiles.
Device Trends tab
The trends tab show the events over a time line. This makes it easy to determine what else went on with the device when an issue starts.
Device Logs tab
The Logs tab shows the Windows Event Log entries for hangs and crashes. These events are captured as they happen the device does not wait for the daily digest to send the information to the switch.
Device Software tab
This tab lists all the software installed on the device with details about the software such as crashes or hangs in the last 24 hours.
Each column can be sorted.
Software product name.
|Product version number.|
|How many devices are reporting.|
|Number of times this software crashed during the last 24-hour reporting period.|
Number of times this software crashed during the last 24-hour reporting period.
Software crash and hang information is obtained from Windows event data. For background information on Windows events and the event viewer refer to https://support.microsoft.com/en-gb/help/302542/how-to-diagnose-system-problems-with-event-viewer-in-microsoft-windows
|Number of performance anomalies detected in this software during the last 24-hour reporting period.|
I/O write KB/s
|Average disk I/O read rate per second during the last 24-hour reporting period.|
I/O write KB/s
Average disk I/O write rate per second during the last 24-hour reporting period.
For background information on analyzing disk storage performance refer to https://docs.microsoft.com/en-gb/archive/blogs/cotw/analyzing-storage-performance
Virtual Memory Usage KB
Average Virtual Memory Usage KB during the last 24-hour reporting period.
For an explanation of Windows Virtual Memory organization refer to https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/physical-and-virtual-memory-in-windows-10/e36fb5bc-9ac8-49af-951c-e7d39b979938 and https://support.microsoft.com/en-us/help/2160852/ram-virtual-memory-pagefile-and-memory-management-in-windows
Processor Time Seconds
|Each instance of the executable will burn processor time. This column gives the average of the total time consumed by each process instance per second. Each instance uses the sum of all time used by each core in parallel. Therefore, it is possible to see more seconds here than in a day (usually 60 x 60 x 24 = 86400) for the whole column, if your system is working extremely hard 24x7. The theoretical maximum would be somewhere near number of cores x seconds per day . Hence 'Processor Time' rather than 'Human Time'|
Processor Time %
This is an easier notion than Processor Time Seconds. This is the average of the processor consumption of each instance. Each instance of this process will have caused different percentages of compute resource in all the processors and cores to be used over time (unless they have specifically requested certain core affinity). For each minute each process is running, a profile of the usage is built for the whole day. This value is the average of all of those samples. There is no way to work out, for any one of the process instances involved, how long any particular instance was running for. This could indicate a process that is going wild with resources, but it would take more investigation on the device to discover for how long this is happening. It is perfectly possible to see all the values in this column adding up to more than 100% as the processes were not necessarily running at the same time.
For further information on Processor time refer to https://social.technet.microsoft.com/wiki/contents/articles/12984.understanding-processor-processor-time-and-process-processor-time.aspx
Responsiveness Impact %
An indicator of how reactive a process is to activity by other processes on the device. Typically, anti-virus products watch and respond to potentially suspicious activity such as increased network traffic. Anti-virus products will differ in their impact on the overall performance of a device.
Responsiveness Impact % is used to indicate how sensitive a process that appears to be to the use of system resources by other processes on a device. For example Security Protection software present on a device may reveal a spike in its activity whenever a new process is started on that device. This would typically be because the Security Protection software may wish to ensure that the new process starting on the device is present in a security white-list. Other software may also react to activity by other processes and by reacting they impact system resource uses, thereby adversely affect the user's experience. So it is useful to be able to identity software with a highest Responsiveness Impact on a device and potentially investigate further.
Responsiveness Impact % represents the proportion the increased CPU activity detected by the 1E Client as a result of performing a set of operating system level operations that can be attributed to a given running process. Examples of these would be Windows registry and resource creation operations.
It is reported as a percentage to normalize results across devices that offer a range of computing power.
For example if software.exe on a device is attributed a Responsiveness Impact of 53% this means that more than half of the spike in CPU usage caused by software monitoring activity on that device can be attributed to software.
Average number of Windows handles used by this software during the last 24-hour reporting period.
For further information on Windows handles refer to https://docs.microsoft.com/en-us/windows/win32/sysinfo/handles-and-objects
For tips on examining open handles for any Windows process refer to https://docs.microsoft.com/en-us/sysinternals/downloads/handle and https://techcommunity.microsoft.com/t5/windows-blog-archive/pushing-the-limits-of-windows-handles/ba-p/723848
Physical Memory Usage KB
Average Physical Memory Usage KB during the last 24-hour reporting period.
Please refer to https://docs.microsoft.com/en-us/sysinternals/downloads/rammap for a useful tool to examine physical memory allocation on a device.
If the account you are viewing Experience with has at least the Global Questioner role, you will also see an Explore button. Clicking this button will launch Tachyon Explorer.
The coverage will be set to the device you were viewing in Experience.