Saltar navegação

No momento esta página não está disponível em seu idioma. Você pode ver uma tradução automatizada utilizando o Google Translate. Não somos responsáveis pelo fornecimento deste serviço e não podemos verificar os resultados.
Se você necessitar mais ajuda fale conosco.

Telemetry

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.

CARTO Telemetry

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.

Telemetry Purpose
Opt out commsNotify the telemetry engine that the customer has set the software suite preference to opt out and no telemetry may be collected.
Opt in commsNotify 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 commsNotify the telemetry engine that the software has been opened and may send further telemetry.
Event commsNotify the telemetry engine of an event occurring within the software. Used to track feature usage.
Crash commsNotify 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 commsNotify the telemetry engine that a session is continuing.
End session commsNotify the telemetry engine that the software has been closed and will not send further telemetry in that session.