Tableau Resource Monitoring Tool - Incidents

Incidents

There are two types of incidents for the Resource Monitoring Tool.

  1. Incidents that are built-in and are set by default - these cannot be configured. When the event occurs, the incident is reported under the Incidents tab:

    Incident Incident Level Description
    Agent Down

    warning

    An incident is logged and reported when either one or more Agents are down, and the RMT Server is unable to communicate with the Agent. By default, an email will be sent to the email specified in the Notifications tab.
    Agent Unlicensed critical

    This can happen if Tableau Server is not properly licensed to use Tableau Resource Monitoring Tool, or due to connection issues. For more information on the possible causes, see Agent Incidents

    By default, an email will be sent to the email specified in the Notifications tab.

    Environment Down critical An incident is logged and reported when Tableau Server is offline. By default, an email will be sent to the email specified in the Notifications tab.
    Extract Failure warning An incident is logged and reported when there is an extract failure in Tableau Server. By default, an email will be sent to the email specified in the Notifications tab.
  2. Incidents that can be configured by you:

    Incidents can be configured and used to help detect when unusual situations occur. Incidents can be configured for a variety of events for both Tableau Server and the server it is running on. Following are the events that you can configure incident thresholds for:

    • Hardware: CPU Usage, Memory Usage, Memory availability, Disk Space, and Disk queue length.
    • Slow queries
    • Slow views

    Incidents can be configured either globally to apply to all environments, or can be customized for each environment.

    Global incidents can be configured by clicking on Configuration under the Admin menu, and clicking on the Incident Thresholds tab. Global configurations are applied to existing environments or any new environments created, unless the environment is using custom thresholds.

    Incidents may also be overridden per environment. Do the following to set a specific environment to use custom thresholds:

    1. Choose Environments under Admin menu and click edit on the environment that you want to use custom thresholds.
    2. At this time the environment has all the global thresholds.
    3. Navigate to the Incident Thresholds tab, and click the Use Custom Thresholds option at the top of the page. This will allow you to create new thresholds or edit the existing thresholds. In addition, from this point forward new or updates to global thresholds will not be automatically applied to this environment.

 

Incident Severity Levels

Incidents are configured with different levels of severity.

Severity Level Key Description
Info information The lowest severity. By default, an email will not be sent when an incident at this level is discovered. Also, the environment status will not be effected.
Warning warning Incidents at this level will, by default, send a notification email when triggered. Also, the environment status will be effected.
Critical critical The highest severity. By default, a notification email will be sent when triggered. Also, the environment status will be effected.

 

To change when emails are sent for incidents using the web interface, see Resource Monitoring Tool Server Configuration

To change when emails are sent for incidents using the configuration file, see RMT Server Configuration File.

Thanks for your feedback!