Sean Miller

New Feature: System Data and Diagnostics

Blog Post created by Sean Miller Employee on Feb 11, 2020

The topic of 'System Data and Diagnostics' is not new news.  We announced these capabilities in 7.1.1 in this blog.  However, in the RSA Identity Governance and Lifecycle 7.2 release we have added additional data points and functionality.

 

It is important to understand the 'System Data and Diagnostics' feature is made up of two key parts:

  • Gathering
  • Sharing

 

All configuration for this feature is done on the Admin->Diagnostics->System Data and Diagnostics page.

 

 

Gathering

This is a scheduled task that runs daily to calculate and store off data points.  Once stored, these data points can queried using the public view PV_TELEMETRY_DATA.  These are extremely useful to show the state of the system, show trends over time (like application onboarding), show return on investment (decreasing trend of rule violations), and highlight gaps (number of orphaned accounts).

 

A key value add of having the gathered data is that it is static data perfect for reports and dashboards instead of real time potentially expensive count queries.

 

Data is gathered from yesterday and beyond to avoid incomplete data for today since the time the gathering runs versus collections and other activities may vary

Sharing

In additional to gathering the data points, it is recommended you configure the system to also share this data with RSA.  This document describes in detail what is collected and shared here.  It is important to note that there is no personal data shared like user information and with the exception of the customer name, there is no other identifying information gathered.  By providing the data to RSA, this helps RSA understand how customers are using the product and where we should be investing, what areas are not being used which helps us make deprecation decisions, and understand the size of deployments and identify opportunities where RSA can have conversations to help our customers.  Lastly, this also helps RSA identify key customers to participate in beta programs or design partnering based on their use of the product.

 

To share the data, the IGL server needs to be able to access the web site - https://cms.netwitness.com/telemetry

 

For additional information on this update – please check out this additional context:

Outcomes