Reporting profiling results

This section describes the different ways of sharing/exploring the results of a profiling job.

Job Execution page

After a Job has been started from the Environment > Jobs screen, clicking on the Job Name will result in the display of the profiling job details. After the Job has been completed, it will display the sensitive data findings on a table-column by table-column or file-field by file-field basis under Profile Results.

When profiling multiple files (mainframe data sets), ASDD makes inventory assignments by averaging results across all files using the same format in the rule set.

PDF report

To retrieve a PDF report, click on the Report and Logs → Job Report at the top of the page.

Rule set page

Alternatively, after a job is completed successfully, the profiling results can be displayed through the Rule Set screen. The view differs by connection type as shown below.

Database Rule Set

Profiling results can be determined by examining the assigned Algorithm for the table(s) in the Rule Set.

File Rule Set

Profiling results can be determined by examining the assigned Domain and Algorithm for the files(s) in the Rule Set.

Mainframe Rule Set

Profiling results can be determined by examining the assigned Domain and Algorithm for the files(s) in the Rule Set.

CSV

To get a spreadsheet capturing the profiling results for the rule set, click on Actions → Export Rule Set from Actions near the top of the page, and a CSV file will be created.

The spreadsheet can then be shared and manually modified to correct the sensitive data findings by:

Changing the Is Masked, Algorithm, and/or Domains fields for the respective Table/Column or File/Field in the CSV file accordingly.
Importing the modified spreadsheet by clicking on Actions → Import Rule Set near the top of the page and specifying the modified CSV file name.

API endpoint

Using the API endpoint /profileResultDatabase/{executionId}, profiling results can be retrieved by providing the executionId. This method is only for database connections and will not work with other connection types. Results will be returned in JSON format.

CODE

{
  "_pageInfo": {
    "numberOnPage": 4,
    "total": 4
  },
  "responseList": [
    {
      "columnMetadataId": 1,
      "columnName": "CITY",
      "tableName": "PROFILE_TEST",
      "domainName": "CITY",
      "algorithmName": "NullValueLookup",
      "dataType": "VARCHAR2",
      "isProfilerWritable": false
    },
    {
      "columnMetadataId": 2,
      "columnName": "COUNTRY",
      "tableName": "PROFILE_TEST",
      "dataType": "VARCHAR2",
      "isProfilerWritable": false
    },
    {
      "columnMetadataId": 3,
      "columnName": "DOB",
      "tableName": "PROFILE_TEST",
      "domainName": "DOB",
      "algorithmName": "DateShiftDiscrete",
      "dataType": "DATE",
      "confidence": 100,
      "isProfilerWritable": true
    },
    {
      "columnMetadataId": 4,
      "columnName": "ADDRESS",
      "tableName": "PROFILE_TEST",
      "domainName": "ADDRESS",
      "algorithmName": "AddrLookup",
      "dataType": "VARCHAR2",
      "confidence": 100,
      "isProfilerWritable": true
    }
  ]
}