Configure the Telemetry Service

Telemetry data tracks the usage of RSA Authentication Manager features and provides reliability and software version information for your Authentication Manager instances. RSA collects this data to better understand product configuration and usage, improve support, and focus development efforts to dramatically improve customer satisfaction. No personal identifiable information (PII) or sensitive information collected.

Telemetry data is sent by each Authentication Manager primary and replica instance. You can download and view the telemetry data that is sent to RSA on the Download Troubleshooting Files page in the Operations Console.

The Telemetry service is automatically enabled and configured when you install or upgrade to RSA Authentication Manager 8.7 SP1. Telemetry data is stored offline. RSA assigns each customer deployment a time to send the data that is between 1:00 AM and 5:00 AM local time. If Authentication Manager is unable to send telemetry data to RSA, then you can configure the telemetry settings.

Before you begin

  • Confirm that your firewall rules allow access to telemetry.access.securid.com and the IP addresses 52.188.41.46 and 52.160.192.135.
  • If your company uses URL filtering, be sure that telemetry.access.securid.com and both IP addresses shown above are whitelisted.

Procedure

  1. In the Security Console, click Setup > System Settings.
  2. Under Advanced Settings, click Telemetry.
  3. Verify that the Enable Telemetry checkbox is selected. Telemetry is automatically enabled when you install or upgrade to RSA Authentication Manager 8.7 SP1.
  4. A proxy server is required if Authentication Manager is behind an external firewall. If you already use a proxy server to connect your deployment to the Cloud Authentication Service, then these fields are pre-filled with the same data.

    If you need to modify these fields, do the following:

    1. Under Proxy Configuration, click Enable Proxy Configuration.
    2. In the Proxy Host field, enter the hostname of the proxy server. For example, example.com. If you have an HTTP proxy server that does not require a certificate, you can enter either a hostname or an IP address.
    3. In the Proxy Port field, enter the port used by the proxy server.
    4. In the Proxy Username field, enter the unique username for the proxy server.
    5. In the Proxy Password field, enter the unique password for the proxy server.
    6. If you made changes to your proxy server configuration, such as changing the username or password, restart the proxy server.
    7. Click Test Connection.
    8. If you are using an HTTPS proxy server, you are prompted to trust a proxy server certificate. Verify the certificate with your help desk or network administrator, and click Yes.

      The trusted proxy server certificate cannot be deleted in Authentication Manager. You can replace the certificate by updating the proxy server connection or by connecting to a new proxy server.

      An HTTP proxy server does not require this step.

  5. In the Save telemetry data field, you can modify the number of days for which you save the telemetry data offline. The default value is 30 days, but you can save one year (365 days) of telemetry data.
  6. Click Apply Settings.

After you finish

To view the telemetry data that is sent to RSA, download the Authentication Manager log files. The telemetry data is in the directory Authentication Manager Logs\server\logs\telemetry. For instructions, see Download Troubleshooting Files.