Troubleshooting Asset

To collect and send information to Tanium for troubleshooting, collect log and other relevant information.

Collect logs

The information is saved as a compressed ZIP file that you can download with your browser.

  1. From the Asset home page, click Help , then the Troubleshooting tab.
  2. Collect the troubleshooting package. Click Collect. To collect additional information Postgres table statistics that includes information bad tuples, live, last vacuum, and so on, click Collect Detailed. When the ZIP file is ready, you can download the tanium-asset-support-[timestamp].zip file to your local download directory.
  3. Attach the ZIP file to your Tanium Support case form or send it to your TAM.

In the ZIP file, you can view the following information: 

  • postgresql-xx.log : Contains Postgres log file.
  • info directory: Contains CSV files for Asset configurations, including attribute configurations, destinations, permissions, and so on. If you click Collect Detailed, a CSV file for postgres statistics (pg-stats.csv) is also created.
  • job directory: Contains logs for the data imports and exports.

Update service account log level

  1. From the Asset home page, click Settings , then the Advanced Settings tab.
  2. Change the Service Account Log Level.
  3. Click Save.

Troubleshoot asset data exports and imports

View status of imports and exports

On the Asset home page, you can view a timeline of the recent imports and exports. The timeline contains each import, with one of the following statuses: 

  • : Scheduled
  • : Successful
  • : Error
  • : Running

View import and export logs

In the ZIP file that you download from the Troubleshooting tab, you can view logs for the data imports and exports. These logs are in the job directory:

ServiceNow exports

ServiceNow export logs are named with the following format: job/date_time_job#_servicenow_config#.log. If you enable Trace level logging on your ServiceNow configuration, numbered subdirectories, for example job/65, are created that contain all of the POST and GET requests for that job. See Add ServiceNow as a destination for more information about configuring logging.

Asset data imports

You can use these logs to view details about the scheduled runs that are occurring to import asset data from Tanium into your Asset database.Tanium data import logs are named with the following format: job/date_time_job#_tanium_1.log. For data you are importing from a database, import logs are named with the following format: job/date_time_job#_database_1.log. To change the log level for imports, see Configuring sources.

Remove unneeded data from the Asset database

You can configure data retention and automatic vacuuming on the Asset database.

  1. From the Asset home page, click Settings , then the Data Settings tab.
    • To purge stale assets that have not been seen by Asset from the database, select Purge Stale Assets. Then, indicate the age of stale data to remove. The minimum number is seven days.
    • To adjust the trigger and amount of work done during automatic vacuuming, adjust the Cost Limit and Size Factor values. The Postgres VACUUM operation reclaims storage that is occupied by dead tuples. By default, the database is vacuumed when 1% of tuples are considered dead, and the cost limit (amount of work per vacuum cycle) is set to 1000.
  2. Click Save.

Uninstall Asset

  1. From the Main menu, click Tanium Solutions. Under Asset, click Uninstall. Click Proceed with Uninstall to complete the process.
  2. Delete any remaining Asset-related scheduled actions and action groups.

  3. Remove Asset Tools from your endpoints. To see which endpoints have the file evidence tools installed, ask the question: Get Asset File Evidence Status from all machines. If you want to clean the artifacts from your endpoints, contact your TAM.
  4. A backup asset-files folder gets created as part of the uninstall process. You can keep or delete this folder. If any other Asset artifacts remain on your Module Server, contact your TAM.

Last updated: 11/6/2018 2:57 PM | Feedback