---
schema_version: "1"
id: 5d10cae9f06263221090fdec0cacfc5a3296a8137df373cac5cb57e497125883
title: Troubleshoot Missing Hardware Performance Data
collection: tableau
version: current
locale: en-gb
portal_url: https://docs.salesforce.com/tableau/current/en-gb/server-linux/rmt-troubleshoot-missing-hardware-perf-data.md
canonical_url: https://help.tableau.com/current/server-linux/en-gb/rmt-troubleshoot-missing-hardware-perf-data.htm
source_site: help.tableau.com
content_type: documentation
content_hash: 1e00843cbabaee75d1d978c9b35b20ee4d4e08c3735f306f44bdac15a3f2684b
description: Troubleshoot missing hardware performance data in the Resource Monitoring Tool.
---
[Skip to main content](#main-content)

# Troubleshoot Missing Hardware Performance Data

Processor (CPU) usage, memory usage, disk queue and network performance stats are considered hardware performance data in the Tableau Resource Monitoring Tool. The most common places to see this data are:

- On the **Environment Overview** dashboard in the Performance and Tableau Processes charts
- On the **Servers** dashboard

This data is reported in near real time by the Resource Monitoring Tool agent processes running on each of your Tableau Server machines.

If these charts show no data for an extended period of time, this may be due to the following reasons:

1. Tableau Server is not licensed correctly. This may be due to missing Advanced Management capabilities. Make sure Tableau Server has the required licence. For more information on Advanced Management, see [About Tableau Advanced Management on Tableau Server](https://help.tableau.com/current/server-linux/en-gb/itm_intro.htm).
2. Connectivity issues between Agent and Tableau Server. Use the steps below to troubleshoot and isolate these issues.

## Step 1: Check the Agent connection status

First, check that the Agents are currently connected to the Resource Monitoring Tool. The Agents send a regular heartbeat message to the RMT Server to indicate their connection status.

1. Log in to the Resource Monitoring Tool as an administrator.
2. Navigate to the **Admin** > **Environments** page.
3. Click the Edit link for the environment that is missing performance data.
4. Locate the **Servers** list and ensure that each server shows the Agent Service as **Connected**. You can hover over the **Connected** status for a timestamp of when the last heartbeat message was received.

## Step 2: Ensure the Agent is running

If the Agent shows as **Disconnected** in the Resource Monitoring Tool, the Agent’s Windows service may not be running.

1. Connect to the machine the agent is running on.
2. Ensure that the Tableau Resource Monitoring Tool Agent Windows service is running.

## Step 3: Ensure the Agent is configured correctly

If the agent shows as **Disconnected** in the Resource Monitoring Tool, but the service is running, the agent may not be able to reach the Resource Monitoring Tool’s message queue.

1. Connect to the machine the agent is running on.
2. Navigate to the agent’s installation folder. For example: `/opt/tableau/tabrmt/agent`
3. Run the _rmtadmin status_ command.

The _rmtadmin status_ command will test the agent’s connectivity to the message queue and the Resource Monitoring Tool’s RMT Server.

## Step 4: Restart the Agent

In some cases, the Agent may be running and all status indicators show success, but the agent continues to not send hardware performance data. This is a known issue that can result from transient connectivity errors between the Agent and the message queue. For example, when restarting the message queue server or during brief network interruptions.

To ensure this isn’t the case, restart the Agent and wait a few minutes to confirm whether the performance data is working again.

1. Connect to the machine that the Agent is running on.
2. Restart the Tableau Resource Monitoring Tool Agent Windows service.
3. Ensure the service starts successfully.
4. Wait at least 10 minutes and then log in to Resource Monitoring Tool and check Servers dashboard to see if any hardware performance data has been received.

## Step 5: Verify Run As account configuration

Ensure the run-as accounts for the agents are configured to use the same run-as account that Tableau Server uses to connect to Tableau Server and get the performance and CPU data. It must be the same account that Tableau Server is configured with. Make sure this account has permissions to access Tableau Server logs.

## Step 6: Contact Support

If, after following the above steps, the issue is still not resolved, please contact support.

The support team will need a copy of the Resource Monitoring Tool log files from the RMT Server and from each of the agents that are having connection issues. For more information on how to collect log files and sending them to Tableau customer support, see [Sending Log Files to Tableau Customer Support](https://help.tableau.com/current/server-linux/en-gb/rmt-admin-logs.htm#SendingLogs).

## Who can do this

Resource Monitoring Tool Administrators.