Telemetry

DA/EE configuration

Enabling or disabling telemetry is a per site concern, and as such it has been set up to be centrally configured. The location of this central configuration is:

C:\ProgramData\Micromine\PITRAM\Configuration\Machine\TelemetryManagerConfiguration.xml

on the machine where GSS resides. GSS provides this configuration to Data Acquisition (DA) and Event Editor (EE)clients.

The server installation will create this file and populate it with the production App Insights connection strings for DA and EE by default. The connection strings will also be rest if they have been modified.

For the Pitram 12.0 install, telemetry is currently not enabled by default. To enable Telemetry, <TelemetryEnabled>true</TelemetryEnabled> needs to be added to the config file.

Note:<TelemetryEnabled>false</TelemetryEnabled> will be considered an explicit opt-out for any future Pitram release installation where telemetry is enabled by default. Removing the TelemetryEnabled tag entirely will disable telemetry, but will not be considered an "opt-out".

There are some measures in place to prevent the Development team from sending telemetry to the production App Insights instances: Granted, this is not crucial while telemetry isn't enabled by default.

The current measures consider:

• Debugger is attached

• A machine's qualified host name contains micromine.com

• A (Hyper-V) VM's physical host name contains micromine.com

If one of those conditions is met:

<AllowInternalDevelopmentTelemetry>true</AllowInternalDevelopmentTelemetry>

needs to be added to the config file to allow telemetry to be sent.

Production App Insights connection strings

Dome configuration

In order to enable telemetry in Dome, please upload the ApplicationInsights.config file (for Administrators).

to the web server (e.g. C:\inetpub\wwwroot\DOME)

If the error message below is showing up at the time Dome is starting up:

Could not load file or assembly 'System.Memory, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Add the following dependentAssembly configuration to the web.config:

<runtime>
    <assemblyBinding >

                 :

                 :
    <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.1" newVersion="4.0.1.1" />
     </dependentAssembly>
  </assemblyBinding>
</runtime>