RSA IGL Services 101: v7.2x new Telemetry Data

Document created by Jamie Pryer Employee on Dec 15, 2020Last modified by Jamie Pryer Employee on Dec 23, 2020
Version 4Show Document
  • View in full screen mode

As part of v7.2x, the RSA IGL team introduced a new telemetry feature, which has some awesome information as part of it. This telemetry data is collected every night and is really useful for using when creating new charts/reports.

The data is all found in this new view: PV_TELEMETRY_DATA

Example can be found here as examples: RSA IGL Recipes - The 12 Dashboards of Christmas - Summary

 

Before reading ahead, check out these 2 documents first:

 

SO WHAT? why do I care about this table and the data?

Good question! The main reasons are that:

  1. This data is collected for you and is much easier to access then creating your own SQL queries. Its all found in a single view = PV_TELEMETRY_DATA
  2. Its also a lot faster, as the data is pre-calculated and stored, so less of a burden on system resources overall (e.g.. you are not running lots of complex SQL queries, across multiple different tables)

 

OK, tell me more...

The telemetry data that is collected, is broken out into various specific category's (shown below).

Within each category, there are various "names" of items, that are being collected each day.

So for each day, you will find there are 100s of data points being collected, which you can then use to create some nice charts/reports with - some of these are found here: RSA IGL Recipes - The 12 Dashboards of Christmas - Summary 

 

The category's include the following product areas: 

  • accessrequest
  • afx
  • collectors
  • deployment
  • modulesandcustomization
  • overview
  • product
  • reports
  • reviews
  • roles
  • rules

 

To get a FULL list of all the different options available, please run the following query within your environment (I use SQL Developer):

select distinct
    category,
    name
from PV_TELEMETRY_DATA
order by category, name asc
;

 

Example screen shot:

 

 

Its worth noting that some of the data is collected per item as well, for example per application or AFX connector. So there is a lot of granular data being collected that is specific to your environment too. 


Working example:

Lets say we wanted to look at the total number of completed review items within your environment. 

  • category = 'reviews'
  • name = 'completed.items.total'

 

This is the SQL we could use, to gather this data:

select distinct
   *
from PV_TELEMETRY_DATA
where category = 'reviews'
    and name = 'completed.items.total'
order by day desc
;

 

As we can see when we run this SQL, the "value" changes over the days, from 84 on 19th Sept, then to 85 on 23rd Sept and onto 95 on the 30th Sept. 

2 people found this helpful

Attachments

    Outcomes