Server telemetry data
Details of 1E product usage statistics gathered by Tachyon to help with 1E's continued product improvement initiative.
What data is collected?
At a high level, the following data is collected:
Instruction usage (by Instruction Definition and by day), and statistics on the type of resources attached to Instruction Definitions
1E Client configuration details, versions, operating system variants, device types, age of installation, last connected time and status, and time zones
Registered Portal applications and Consumers
Database table sizes
1E server component information and basic configuration
(Anonymized) Management Group information (number of devices)
1E upgrade history
1E will periodically send summarized, statistical information about usage of the product to 1E. This enables 1E to improve your experience with 1E as it helps us understand how features are being used, focus future development, ensure we continue to support the Operating Systems you currently use, spot early warning signs of potential issues and identify instructions that may be causing issues or could be improved. No personally identifiable data is collected. The data is compressed, encrypted and sent to 1E through email.
Note
By default, 1E collects data continuously and sends a compressed and encrypted summary by email to 1E every Friday at 23:40 UTC.
For on-premises installations of 1E platform, customers have the option to configure the frequency this data is sent to 1E. This option is not available for customers using SaaS versions of the platform, SaaS customers should contact their 1E Account Team.
Metrics
The following tables list all the telemetry metrics. Numeric values are integers unless otherwise stated.
Purpose | A row for each registered Portal application and its current version |
|---|---|
Instance format | ApplicationName |
Example instance | Endpoint Troubleshooting |
Value format | Version number |
Example value |
|
Notes | Sourced from |
Purpose | A row for number-of-months-ago, and how many 1E clients were "first seen" within that number of months ago |
|---|---|
Instance format | NumberOfMonthsAgo |
Example instance | 7 |
Value format | Count of number of devices |
Example value |
|
Notes | Sourced from Based on calendar months, rather than multiples of 30 days - e.g. if today is 2nd July, a device "first seen" on the 30th June will be counted as first seen as one month ago. An instance of zero means "within the last month". Can be used to determine client deployment rate. |
Purpose | A row for each unique combination encoded of 1E Client configuration reported by 1E Client telemetry, and the number of clients in that configuration state |
|---|---|
Instance format | "1EClientConfiguration" |
Example instance | "NM:E0505,PX:0,TAC:40AA4A,TAI:3FFE3,TUI:60080006" |
Value format | Number of clients with that configuration |
Example value | 88 |
Notes | Sourced from |
Purpose | A row for each combination of current online/offline status, Switch identifier and connectivity flags, and the number of clients in that state |
|---|---|
Instance format | OnlineStatus|SwitchId|ConnectivityFlags |
Example instances | Online|1|384 Offline|0|384 |
Value format | Count of number of devices for that combination |
Example value |
|
Notes | Sourced from Where devices are offline, their connection flags represent the values as they were at the time of their last connection. |
Purpose | A row for day-based milestones, and the number of clients which have been "seen" (i.e. connected to the Switch) within that milestone. |
|---|---|
Instance format | NumberOfDays |
Example instance | 7 |
Value format | Count of number of devices |
Example value |
|
Notes | Sourced from Milestones are 1, 2, 4, 7, 30, 90 and 365 days. The numbers will be cumulative, because a device which has been since in the last 1 day will also be counted in 2 days, 4 days, 7 days, etc. |
Purpose | A row for each combination of operating system variant and architecture, and the total number of devices running that OS |
|---|---|
Instance format | DeviceType|OsVersionText|OsArchitecture|VirtualizationPlatform |
Example instances | Desktop|CentOS Linux release 8.2.2004 (Core) |x64|Hyper-V Desktop|Red Hat Enterprise Linux release 8.1 (Ootpa)|x64|Hyper-V Desktop|Ubuntu 18.04.4 LTS|x64|Hyper-V Desktop|Windows 10 Pro N 2004|x86|Hyper-V Desktop|Windows 7 Enterprise|x86| <- absence of Virtualization platform implies physical device Server|Windows Server 2016 Standard 1607|x64| |
Value format | Count of number of devices running that OS variant |
Example value |
|
Notes | Sourced from |
Purpose | A row for each timezone in which client devices exist, and the number of client devices in that timezone |
|---|---|
Instance format | TimeZoneIdentifier |
Example instances | Europe/London Asia/Calcutta |
Value format | Count of number of devices detected in that timezone |
Example value |
|
Notes | Sourced from |
Purpose | A row for each combination of 1E Client variant and version, and the total number of devices running that client |
|---|---|
Instance format | ClientVariant|ClientVersionNumber |
Example instances | Windows|5.1.0.885 Linux|5.0.0.234 |
Value format | Count of number of devices running that variant/version of the 1E Client |
Example value |
|
Notes | Sourced from |
Purpose | A row for each Tachyon server component, and the number of registered instances of that component |
|---|---|
Instance format | Component |
Example instances | BackgroundChannel SwitchConfiguration.2 |
Value format | For components other than the Switch, a count of instances of that component For Switch components, a pipe-delimited sequence of:
|
Example values | 2 (for non-Switch components) SwitchConfiguration.2,1 w|10 s|5 seclvl|1 switches|1 cores |
Notes | Sourced from |
Purpose | A row for each registered Tachyon API consumer, and whether it is flagged as enabled |
|---|---|
Instance format | Consumer |
Example instance | CmConsoleExtensions |
Value format | 0 = disabled, 1 = enabled |
Example value |
|
Notes | Sourced from |
Purpose | A row for each registered instruction definition, showing its total usage to date |
|---|---|
Instance format | Instruction Definition Name|Instruction Definition Version |
Example instance | 1E-Explorer-TachyonAgent-AgentConnectionDiagnostics|17.3 |
Value format | Pipe-delimited sequence of:
All the values above are based on the sum of all executions of that instruction definition. |
Example value | 2 use|900 targeted|876 sent|1 no_data|3 error|7 not_impl|0 too_large|52286 success_rows|17 mb_sent|35 mb_recv|208 mb_urecv |
Notes | Sourced from If an instruction definition is updated, this row reflects usage only of the most recent version of that instruction definition. |
Purpose | A row for each type of instruction resource (i.e. file attached to an instruction definition), and the total number of resources of that type |
|---|---|
Instance format | ResourceType |
Example instance | Perl |
Value format | Total number of resources of that type |
Example value |
|
Notes | Sourced from |
Purpose | A row for each type of instruction resource (i.e. file attached to an instruction definition), and the total size of resources of that type |
|---|---|
Instance format | ResourceType |
Example instance | PowerShell |
Value format | Total size in kilobytes |
Example value |
|
Notes | Sourced from |
Purpose | A row for each day of system usage, and the instruction usage and network traffic (through instructions) incurred on that day |
|---|---|
Instance format | Localized date/time |
Example instance | 8/4/2020 12:00:00 AM +01:00 |
Value format | Pipe-delimited sequence of:
All the values above are based on the sum of all executions of instructions on that day. |
Example value | 19 instr|94 targeted|94 sent|28 no_data|36 error|0 not_impl|0 too_large|2419 success_rows|0 mb_sent|0 mb_recv|1 mb_urecv |
Notes | Sourced from |
Purpose | A row for each management group (as defined in TachyonMaster), and the number of devices within that management group |
|---|---|
Instance format | ManagementGroupId|ManagementGroupType |
Example instance | 76|2 |
Value format | Number of devices in that management group |
Example value | 777 |
Notes | Sourced from Management group types are (System = 0, Internal = 1, External = 2) |
Purpose | A row for each table in the TachyonMaster database, and statistics about that table usage |
|---|---|
Instance format | TableName |
Example instance | PolicyRuleStatus |
Value format | Pipe-delimited sequence of:
|
Example value |
|
Notes | Sourced from SQL table metadata; this data may not be available if the account used to perform the query does not have permissions to query sys.* tables for TachyonMaster database. The query to derive this information is based on the query used by SQL Server Management Studio to build the "Disk Usage" report. |
Purpose | A row for major/minor database install/upgrade event, and the date/time of that event |
|---|---|
Instance format | VersionNumber |
Example instance | 5.1.0.607 |
Value format | Localized date/time |
Example value | 8/4/2020 11:10:33 PM +01:00 |
Notes | Sourced from The version number is derived from the "SourceVersion" column, which typically is the binary version of the database resource DLLs containing the database changes to apply. Hotfixes will only be registered if they perform a database change. |