Troubleshooting Reporting

If Reporting is not performing as expected, you might need to troubleshoot issues.

Collect logs

The information is saved as ZIP files that you can download with your browser.

  1. From the Main menu, go to Data > Settings.
  2. From the Troubleshooting tab, select the solutions for which to gather troubleshooting packages and click Create Packages.
    By default, all solutions are selected.
  3. When the packages are ready, click Download Packages.
    ZIP files of all the selected packages download to the local download directory.

    Some browsers might block multiple downloads by default. Make sure to configure your browser to permit multiple downloads from the Tanium Console.

  4. Contact Tanium Support to determine the best option to send the ZIP files. For information, see Contact Tanium Support.

Unable to view or select content

In environments that enable role-based access control (RBAC), users cannot access content to which they do not have permission. Sensors, sources, and reports are among those objects that are managed through RBAC. If you are unable to access sensors, sources, or reports in Reporting, make sure your user account has sufficient permission to the content sets to which those objects are assigned.

  • You must have read permission to the content set to view content in the content set. For example, if you do not have read permission to Patch sensors, you will not see Patch sensors as options when registering those sensors in Tanium Data Service.
  • You must have write permission to a content set to add, edit, or delete content in the content set. For example, if you do not have the Report write permission to a content set, you cannot edit any reports that are assigned to that content set.
  • To view a report, you must have the Report read permission to the content set that contains the report.
  • If you cannot view the Reporting workbench, make sure your user role contains the Report API user permission.
  • Certain sensors, such as sensors that provide duplicate data, are intentionally unavailable in Reporting, even if you register the sensors in Tanium Data Service. Expand the following section to view a list of sensors that are unavailable in Reporting.

ClosedUnavailable sensors in Reporting

  • Client Extensions - Installed Extensions
  • Compliance Rule Failures
  • Comply - Compliance Exposure Score
  • Comply - Compliance Results
  • Comply - NMap Scan Results
  • Comply - Oval Findings
  • Comply - Vulnerability Results
  • Computer Groups
  • Discover - Is Unmanageable
  • Discover Label
  • Discover Location
  • Discover Method
  • Discover Profile
  • Discover Satellite
  • Domain Member
  • EID Last Changed
  • Impact - Active User Session SIDs
  • Impact - Administrator SIDs
  • Impact - Computer Domain SID
  • Impact - Physical NetBIOS Computer Name
  • Is AIX
  • Is Linux
  • Is Mac
  • Is Solaris
  • Is Windows
  • Last Discovered
  • Map - Endpoint Health
  • Number of Fixed Drives
  • Online
  • Patch - Patch List Applicability
  • Unmanaged Assets
  • x64/x86?

Empty fields when viewing a single endpoint

When you view the details for a single endpoint, some fields might be empty. The following are some reasons why fields might be empty.

  • Reportinguses registered sensors in Tanium Data Service to retrieve the details for a single endpoint. If a sensor is not installed, the fields that the sensor provides are empty.
  • If a sensor is not registered with Tanium Data Service, the fields that the sensor provides are empty. To register sensors with Tanium Data Service, see Tanium Console User Guide: Manage sensor results collection.
  • If you do not have RBAC permissions to use the sensor, the corresponding fields that the sensor provides are empty. Contact your administrator for additional permissions.
  • If the sensor is quarantined, the fields that the sensor provides are empty. For information about quarantined sensors, see Tanium Console User Guide: Managing sensor quarantines.

Version and disk usage details

If you need to contact Tanium Support to troubleshoot an issue with Reporting, you may need to provide your version of Reporting and how much disk space Reporting uses.

From the Reporting Overview page, click Information . The version information and storage size appear in the About tab.

Uninstall Reporting

When you uninstall Reporting, any collected data is saved by default so that you can restore the data if you later decide to reinstall Trends. In some cases, you might want to start "clean" and not restore the data. To do this, you must manually uninstall some files.

Consult with Tanium Support before you uninstall or reinstall Trends.

What happens when you uninstall Reporting?

When you uninstall Reporting, the Tanium Console removes:

  • Reporting workbench
  • Reporting-related configuration objects (reports and dashboards)
  • Reporting service

To support data restoration, the uninstallation procedure does not remove:

  • Collected data at <Tanium Module Server>\services\reporting-files\
  • Exported reports
  • Data sources
  • Reporting content set

Uninstall Reporting so data is restored when you reinstall

  1. Sign in to the Tanium Console as a user with the Administrator role.
  2. From the Main menu, go to Administration > Configuration > Solutions.
  3. In the Content section, select the checkbox for Reporting and click Uninstall.
  4. Review the summary and click Uninstall.
  5. If prompted to confirm, enter your password and click OK.

If you later install Reporting, the previous data is restored.

In an Active-Active deployment, the Reporting workbench and Reporting menu remain on the cluster member on which the uninstallation was not run. The Reporting workbench must be manually removed from that instance. Contact Tanium Support for assistance. For information about Active-Active deployments, see Tanium Core Platform Install Guide: Installing Tanium Server in an Active-Active cluster.

Uninstall Reporting so you start fresh when you reinstall

  1. Uninstall Reporting as described in the previous section.
  2. Manually delete the following:
    • Reporting files at <Tanium Module Server>\services\reporting-files\

If you later install Reporting, no data is preserved from previous installations.

Contact Tanium Support

To contact Tanium Support for help, sign in to https://support.tanium.com.