No Data in 'Cache Hit/Miss Analysis,Concurrent Users,Vizql Bootstrap Activity'

[suren-pratap]

Hi,

I have setup TabMon on one of Tableau Server installed node. All the tabs are displaying data except below mentioned tabs:

1. Cache Hit/Miss Analysis
2. Concurrent Users
3. Vizql Bootstrap Activity

Environment:-

1. Tableau Server Version: 2019.3.2 (20193.19.1110.1722) 64-bit Windows
2. Tabmon

Please suggest the steps to fix the issue.

[akeies]

same here I'm using Tableau server 2019.2.2 and Tabmon 1.4 still can't see Cache hit/ Concurrent User and VizQL bootstrap activity , kindly help. thank you

[danjrahm]

Hello,

Can you send me the TabMon logs? They are found here:
\TabMon\Logs\TabMon.log.txt

Once I have these I should be able to take a look.

Thanks,
Dan

[ivmonnier]

Hello,

was there any result for this?
I have Tableau Server 2020.4, just installed Tabmon, and getting very useful info in the provided workbook except for

• Cache Hit/Miss Analysis
• Concurrent Users
• Vizql Bootstrap Activity

In fact, I first tested on my dev server and I had some info.
I changed the config to monitor my prod server and then, the fields "invocation_count" and "exception_count" have no value.

I attach my logs in case of.

Thank you

Ivan
20210420_TabMon.log.txt

[danjrahm]

Hello,

Thank you for sending the logs. It looks like TabMon is running into a closed JMX ports.

2021-04-20 16:10:03,586 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Scanning JMX port(s) "8664, 8487"
2021-04-20 16:10:25,409 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8664), stopping scan.
2021-04-20 16:10:46,414 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8487), stopping scan.
2021-04-20 16:10:46,414 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Scanning JMX port(s) "8537"
2021-04-20 16:11:07,409 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8537), stopping scan.
2021-04-20 16:11:07,409 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Scanning JMX port(s) "8568, 8362, 9000, 8158"
2021-04-20 16:11:28,412 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8568), stopping scan.
2021-04-20 16:11:49,408 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8362), stopping scan.
2021-04-20 16:12:10,407 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (9000), stopping scan.
2021-04-20 16:12:31,412 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8158), stopping scan.
2021-04-20 16:12:31,412 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Scanning JMX port(s) "8728, 8694"
2021-04-20 16:12:52,424 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8728), stopping scan.
2021-04-20 16:13:13,421 [5] DEBUG TabMon.Counters.MBean.MBeanClientFactory - Encountered closed JMX port (8694), stopping scan.

Was JMX enabled on production Tableau Server instance and was the TabMonConfigurationBuilder tool run?

To configure JMX please follow the steps under "Configure Tableau Server" here.

To run TabMonConfigBuilder please follow the steps under "Using TabMonConfigBuilder.exe To Help Build TabMon.config" here.

If there are still issues after checking these settings, please let me know.

Thanks,
Dan

[ivmonnier]

Hello Dan,

thank you for replying.

The JMX ports on Tableau Server are opened, I just ran
PS D:\Dev\Tableau_serveur\PShel> tsm configuration get -k service.jmx_enabled
true

I also ran the TabMonConfigBuilder to get the right port numbers.

I have read a post where someone wrote that, even after running the command, some ports remained closed.
I do not know what to do in this case.

Ivan

[ivmonnier]

In the logs, it is possible to have "closed port" comments, when I started, I had not run TabMonConfigBuilder and it was scanning the wrong ports.

If you look further downin the logs I think this does not occur any more.

Ivan

[danjrahm]

Hello,

TabMon will only scan the JMX ports to create JMX clients during the initialization phase of TabMon. If the JMX ports are closed and TabMon doesn't run into any exceptions, it will continue to sample any valid counters (normally Perfmon counters).

The line "Loading MBean counters.." after the initialization step may be a bit confusing. While TabMon is attempting to load ephemeral counters at that point, we don't support MBean (JMX) ephemeral counters. To pick up newly opened JMX ports, TabMon will need to be restarted.

Within the logs, I can only see one attempt to initialize TabMon. At that point TabMon encounters the closed JMX ports and moves on. This leads me to believe that TabMon is either not configured with the correct JMX ports or Tableau Server is not properly opening up the ports.

After running tsm configuration get -k service.jmx_enabled true did you also run tsm pending-changes apply? This is needed to apply the changes.
If the changes weren't applied, please run the two commands again, followed by the TabMonConfigBuilder.

After the steps above are followed, if Tableau Server is still failing to open the JMX Ports, Tableau Technical Support may need to be contacted. They cannot help with the configuration of TabMon but they may be able to assist in opening up the JMX ports.

Thanks,
Dan

[ivmonnier]

Hello Dan, thank you for your reply.

I did it all again:

• tsm configuration set -k service.jmx_enabled -v true
  tsm pending-changes apply
• tsm topology list-ports > tserver_ws01_ports.txt
• tabmonconfigbuilder tserver_ws01_ports.txt tserver_ws01_config.txt
• stopped and restarted tabmon

and I still have the message "Encountered closed JMX port (xxxx), stopping scan." on every single port listed in the config file.

The other measures (CPU, RAM, disk...) are ok.

I will log a case at Tableau.

Best regards

Ivan
TabMonConfig.zip