Table of Contents

Telemetry

Diagnostic telemetry data is used to keep Altus secure and up-to-date, detect, diagnose and remediate problems, and also make product improvements.

Our telemetry collects:

  • Metadata: Data about customer data, e.g. counts of the types records in use.
  • Performance Data: e.g. How long do operations take? How long to pages take to load?
  • Behavioural Data: e.g. What features are most popular? How do users prefer to work with their data?

This data does not include:

  • Personal Data: e.g. a user’s name or email address
  • Customer Data: e.g. the content of the user’s files, or the contents of projects, programs or portfolios managed by the product

Our system uses a unique ID associated with user’s diagnostic data. For example, if we receive diagnostic data showing that one of our apps crashed 100 times, this unique ID lets us determine if it was a single user who crashed 100 times or if it was 100 different users who each crashed once. We don’t use this unique ID to identify a specific user.

Altus uses Microsoft Application Insights for Telemetry collection management and storage. Altus collects the following telemetry data items in addition to the default items collected by Microsoft Application Insights:

  • Tenant ID
  • Tenant Name
  • Application ID
  • Application Name
  • Organisation Unique Name
  • Organisational Currency ID
  • User ID (guid)
  • User TimeZone offset
  • User Security Roles
  • Browser Language
  • Table Type Displayed
  • Event Type Action
  • Dataverse Storage Metrics

In addition to telemetry collected by Altus, platform vendors may also collect telemetry:

Note

Altus will never share organisational specific telemetry with a 3rd party unless required to do so by law, or via express written permission.

Telemetry Settings

An Altus customer can opt out of telemetry via settings in the Altus configuration settings area. There are two settings related to telemetry, InstrumentationKey and TelemetryConnectionString.

Either a key or a connection string may be provided. If both are provided, the connection string takes priority. If the setting is set to 'false', then telemetry will be disabled.

Setting Description
InstrumentationKey Used to provide the instrumentation key. If set to 'false', telemetry collection is disabled.
TelemetryConnectionString Used to provide the connection string. If set to 'false', telemetry collection is disabled.
FeedbackOptOut If set to 'true', disables the collection of user feedback.

User Feedback Prompts

As of version 2022.05.31.3, users will periodically be prompted for feedback ratings in Altus. Customers can modify the cadence of feedback rating prompts to users. Note that if FeedbackOptOut is set to true, no prompts will occur regardless of the cadence setting.

Setting Description
userFeedbackCadence Sets the number of days between feedback rating prompts. First-time users will be prompted after 30 days. The default cadence after the first prompt is 90 days. Setting this value to 0 will disable feedback prompts.

Telemetry for Documentation Usage

Content served by this website utilises the following telemetry services:

  • Google Analytics
  • LinkedIn Analytics
Edit this page