Telemetry tasks of Dispatcher

At Topology > Dispatchers, you can assign the Telemetry role to one or more Dispatchers, so you will have control on which Dispatcher the telemetry tasks will be executed. Only one Dispatcher will be responsible for running the telemetry tasks at one time. For performance reasons, it is advised to choose a Dispatcher near the Datastore. The Dispatcher needs Internet access to communicate with the telemetry web server.

Telemetry tasks include:

• Collect and report back on:
  • How many Agents and Agents+ are deployed
  • Which Tasks are executed and how many times

For a complete list of collected data, see Telemetry.

Important: The Telemetry functionality enables software and hardware information related to the Ivanti product and/or the environment in which the product is utilized, to be collected and provided to the Ivanti Research and Development team. This information may contain aggregate or statistical information about the use of the Ivanti product and the type of system(s) and related database(s) in which the Ivanti product is deployed. This data contains no information that could reasonably be used by Ivanti to directly identify a person. Installing this version of Ivanti Automation that includes the Telemetry functionality means that you allow Ivanti to receive and use this information for research, analytics and improvement of its products. The information provided to Ivanti is considered non-confidential.

Configuration

At Topology > Dispatchers, on the Settings tab of the Dispatcher’s properties, you enable the setting Telemetry to assign the Telemetry role to the selected Dispatcher. To enable the setting for multiple Dispatchers, you can also use the option Change settings of selected Dispatchers from the context menu or settings overview. The same procedure applies to disable the Telemetry role.

Perform telemetry tasks

When the Dispatcher starts, it tries to contact the telemetry web server to check for an Internet connection. If the connection has been established successfully, the Dispatcher will check every 5 minutes if it needs to run or take over the telemetry task. If no connection could be established, the Dispatcher will wait until the Dispatcher restarts and try again. Depending on the configuration of the Dispatchers, several scenarios are possible:

• One or more Dispatchers have been assigned the Telemetry role and (some of them) are online: The first available Dispatcher with the Telemetry role will run or take over the telemetry task.
• All Dispatchers that have been assigned the Telemetry role are offline: The first available Dispatcher will run or take over the reporting task.
• No Dispatchers have been assigned the Telemetry role: The first available Dispatcher will run or take over the telemetry task.

Once every 30 days, one Dispatcher will do the collection just before sending the data (if a successful Internet connection could be made). The telemetry action is logged in the Audit Trail.

Overview Telemetry role

Depending on the scenario a different value will be shown in the column Roles in the Dispatchers overview. That way you can see which of the Dispatchers are currently performing the telemetry tasks. The values for this column are:

Dispatcher role	Definition
<empty>	The Dispatcher is not assigned any role and is not performing telemetry tasks.
Telemetry	The Dispatcher is assigned the Telemetry role, but currently not performing telemetry tasks.
Telemetry*	The Dispatcher is assigned the Telemetry role and is performing telemetry tasks.
(Telemetry)*	The Dispatcher is not assigned the Telemetry role, but is performing telemetry tasks.

Please note that only one Dispatcher will show the * at one time.