Generating reports

You can configure Health Check to automatically generate TPAN reports on a regular schedule, or you can manually generate a TPAN report. For each report that is stored on disk, you can download an HTML or compressed ZIP file.

Run a TPAN report manually

To generate a TPAN report manually, click Run TPAN Report Now in the Manual Report Generation section of the Health Check Overview page.

Automatically generate TPAN reports

To automatically generate TPAN reports, Set the collection schedule. To change the schedule, click Collection Schedule in the Health Check Settings.

Download a TPAN report

Each report that is stored on disk has both a sanitized and a full version. The sanitized versions do not include any potentially sensitive or confidential information like passwords, computer names, or IP addresses. Health Check retains only a configurable number of reports on disk to minimize disk space.

For a sanitized report, you can download a compressed ZIP file. From the Reports section of the Health Check Overview page, click Zip next to a sanitized report to download the TPAN report.

For a full report, you can download an HTML or ZIP file. From the Reports section of the Health Check Overview page, click HTML or Zip next to a full report to download the TPAN report.

Share a sanitized TPAN report

You can manually share the sanitized version of a specific TPAN report. Fom the Reports section of the Health Check Overview page, click Share next to a sanitized report to share the TPAN report.

To automatically share sanitized versions of TPAN reports every time a TPAN report is generated, enable automatic sharing of reports. For more information, see Set the sharing preferences.

Reference: Sample sanitized report

The data in a sanitized report is limited to data about the Tanium instance, not data about the customer-managed environment. You can view exactly what data is included in the sanitized report by downloading the report prior to sharing it with Tanium or enabling automatic sharing of reports.

The sanitized TPAN report includes the following files:

SanitizedPlatform.json

This file is a machine-readable file that contains sanitized data about the Tanium deployment, not data about the customer-managed environment. It includes active and trending client counts, summaries of the volume of questions and actions that were issued, information to determine the health of the Tanium Server host system, the version of each installed solution, and global tuning parameters.

SanitizedPlatform.txt

This file is a human-readable file that details basic information about the state of the Tanium deployment. It contains the latest TPAN date and version, the Tanium Platform version, high-level client counts, leader percentage, string summary information, security modes enabled, such as SAML or TLS, the installed modules and their versions, and any findings from the latest TPAN.

SanitizedTotesEvents.json

This file contains anonymized data about the use of the content within the Tanium deployment. Sensor names that are not published by Tanium or are not signed by Tanium are sanitized to __SANITIZED_UNSIGNED_SENSOR__ to ensure that names of custom sensors that are created by customers are not included. This data helps Tanium understand where various pieces of content are deployed, how widely they are used, and can be used to alert customers if critical issues in a content pack are discovered.

Sample Tanium sensor entry

{
"datetime": 2020-06-08T15:40:04", // Last used timestamp
"hash": 1744818157, // Hash of the sensor
"qid": 63, // ID of the last question in which this sensor was used
"sensor": "Tanium Client Subnet", // Name of the sensor
"signed_status": "Tanium Signed", // Whether this sensor is signed or unsigned
"soln_category": "Core", // Content category into which the sensor was imported
"soln_id": "01-001-0001", // Tanium solution ID with which the sensor is associated
"soln_name": "Initial Content - Base", // Name of the solution in which the sensor is included
"soln_version": "7.1.14.0000", // Version of the solution
"type": "ad-hoc", // Last used in an ad-hoc or saved question
"user": 1 // User ID that last used this sensor
},

Sample customer sensor entry

{
"datetime": 2020-06-04T20:49:43",
"hash": 965165056,
"qid": 55, "sensor": "__SANITIZED_UNSIGNED_SENSOR__",
"signed_status": "Likely Unsigned",
"soln_category": null,
"soln_id": null,
"soln_name": null,
"soln_version": null,
"type": "automatic",
"user": 1
},