In some cases, the Resource Monitoring Tool would allow a new environment to be created that had the same name of an environment pending deletion.
Resource Monitoring Tool upgrades will now apply a configuration change that will allow Postgres connections on FIPS-enabled servers.
During the initial setup, the wording for the 'Host' field requirements of the Resource Monitoring Tool has been updated to reflect that this field should rarely be changed.
The Resource Monitoring Tool listened over port 9001 by default rather than port 80 after initial setup was complete.
In some scenarios, the Resource Monitoring Tool showed null values in the 'Last Executed' field for data queries.
The Chargeback report of the Resource Monitoring Tool would not populate with data when multiple environments were configured and one of the Tableau Server environments had no data.
In the Resource Monitoring Tool, the 'Site' filter on the 'Insights' page did not properly filter the extract refresh list.
The Resource Monitoring Tool failed the initial setup when a fully qualified domain name was provided in the host field. The default security certificate now accepts fully qualified domain names for the host.
During Agent registration in the Resource Monitoring Tool, the final 'Register Agent' button was enabled before the page redirect occurred.
The axes on the Resource Monitoring Tool 'Insights' chart was not aligned for average and maximum values.
The "rmtadmin" command line tool failed to execute and logged an exception when not run from an elevated permission command prompt.