Monitor and Maintain a Tableau Deployment41% of the exam

Observability with RMT, logs, JMX and Activity Log

Map observability requirements to the Resource Monitoring Tool, logging levels, JMX, PerfMon or sysstat and the Activity Log; interpret what they report, revise the topology from it, check inter-node connectivity, and set up Activity Log delivery on Tableau Server and Tableau Cloud.

Official exam objective
3.4 Maintain and tune a Tableau Server environment by using observability data: 3.4.1 Map the features and capabilities of the Tableau Server Resource Monitoring Tool to observability requirements; 3.4.2 Recommend a strategy for collecting and analyzing Tableau Server logs; 3.4.3 Recommend a strategy for collecting and analyzing Tableau Server process metrics; 3.4.4 Recommend a strategy for collecting and analyzing operating system and hardware-related metrics; 3.4.5 Interpret observability data; 3.4.6 Revise architecture based on observability data; 3.4.7 Troubleshoot connectivity in a single or multi-node environment, especially database connectivity; 3.4.8 Configure and implement Activity Log for Tableau Cloud or Tableau Server.

~7 min read · 20 practice questions

What the exam expects

  • Map observability requirements to Resource Monitoring Tool (RMT) features, and recognize what RMT cannot see.
  • Recommend strategies for Tableau Server logs, process metrics (JMX) and operating system and hardware metrics.
  • Interpret RMT status and incidents, and revise the architecture from observability data.
  • Troubleshoot connectivity between nodes and to the repository.
  • Configure the Activity Log on Tableau Server and on Tableau Cloud.

Key terms: RMT (Resource Monitoring Tool: an Agent on every node plus RMT Server, requires Advanced Management); incident (an RMT alert with severity Info, Warning or Critical); JMX (Java Management Extensions, used by tools such as JConsole to read Java process metrics); Activity Log (Advanced Management event logs for auditing, including permission changes); environment (one Tableau Server installation or cluster in RMT).

Key facts

RMT Server minimum
Detail
8 cores, 64 GB RAM; up to 10,000 views per hour
Not monitored
Detail
External repository and gateway status; External File Store status and sizes
Slow Query default
Detail
Warning at 30 seconds; config in milliseconds
Status polling
Detail
30 seconds, background.pollRates.processStatus
Blueprint thresholds
Detail
CPU 80% for 5 min; memory 25%, disk 20% available
Default log level
Detail
info; reset a key with -d
Secure JMX
Detail
tsm maintenance jmx enable, readonly default, restarts
Port listing
Detail
tsm topology list-ports, all nodes
Data Engine CPU limit
Detail
75% average default; 95% on dedicated nodes
Cloud S3 key
Detail
Single-region KMS key; multi-region unsupported
Cloud S3 retention
Detail
S3 Lifecycle configuration
Sources for this section (11)
  • How much CPU and memory does an RMT Agent typically use on recommended hardware?
  • When is an RMT environment Critical even though no critical incident occurred today?
  • When a cluster's logging levels change, which node do you set them from?
  • How often should TabMon sample, and how much data should it keep?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Tableau Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 18 lessons of the Tableau Architect guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Practice exams purchase adds inline bank questions and topic practice (20 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Choose guide-only, practice-only, or save $4 with both

Practice for the Tableau Architect exam