Cette page n'est pas disponible actuellement dans votre langue. Vous pouvez en afficher une traduction automatique avec l'outil Google Translate. Cependant nous déclinons toute responsabilité quant à ce service et nous ne contrôlons pas les résultats de la traduction.
Pour en savoir plus à ce sujet, contactez-nous.
What is telemetry?
When you install or update a Renishaw product, you may be presented with an option to share telemetry with us. Telemetry is valuable technical information that Renishaw would like to collect about the operation of our products and the way that they are used in order to:
- Monitor how well a product, product version or individual features of a product perform in order to enhance performance and improve usability;
- Highlight errors for troubleshooting and remedial purposes, including identifying whether errors have a common cause (e.g. particular product settings, hardware or software configurations, or driver versions);
- Assess the popularity of features in order to inform future product development or retirement decisions; and
- Monitor which product versions or operating systems are still being used in order to inform product security and life cycle decisions.
The following table outlines the telemetry data that is collected by Renishaw's CARTO product suite.
Upon receipt of telemetry, the telemetry engine attempts to geolocate an IP address to city level only, and then disregards such IP address. The telemetry collected does not identify customers or individuals. It is hosted on Renishaw's Microsoft Azure tenancy in Europe.
|Opt out comms||Notify the telemetry engine that the customer has set the software suite preference to opt out and no telemetry may be collected.|
|Opt in comms||Notify the telemetry engine that the customer has set the software suite preference to opt in and that the software suite is permitted to send telemetry.|
|Begin session comms||Notify the telemetry engine that the software has been opened and may send further telemetry.|
|Event comms||Notify the telemetry engine of an event occurring within the software. Used to track feature usage.|
|Crash comms||Notify the telemetry engine of a crash/exception occurring within the software. Used to track issues and capture information on bugs for prioritisation and potential resolution.|
|Heartbeat comms||Notify the telemetry engine that a session is continuing.|
|End session comms||Notify the telemetry engine that the software has been closed and will not send further telemetry in that session.|