Configuration of RabMQChannelTest

This test test reports useful metrics on the message traffic and message prefetching on a channel. This way, the test provides administrators with effective pointers on how to tweak the Prefetch count setting and optimize RabbitMQ performance.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the host for which the test is to be configured.

• In the PORT text box, specify the port at which the configured Host listens; by default, this is 15672.

• The eG agent connects to the Management Interface of the rabbitmq-management plugin of the target node, and runs HTTP-based API commands on the node using the plugin to pull metrics of interest. To connect to the plugin and run the API commands, the eG agent requires the privileges of a user on the cluster who has been assigned the ‘monitoring’ tag. If such a user pre-exists, then configure this test with the USERNAME and PASSWORD of that user. On the other hand, if no such user exists, then you will have to create a user for this purpose using the Management Interface. The steps for this have been detailed in Monitoring RabbitMQ Cluster document. In this case, make sure you configure this test with the USERNAME and PASSWORD of the new user. Finally, confirm the password by retyping it in the CONFIRM PASSWORD text box.

• By default, the SSL flag is set to No, as the target node is not SSL-enabled by default. If the node is SSL-enabled, then set this flag to Yes.

• By default, the NUM DD MESSAGES parameter is set to 10. This means that, by default, the detailed diagnosis of the count measure will report the details of the top-10 channels in terms of their reduction count. To view the details of more channels as part of detailed metrics, you will have to increase the value of this parameter. Likewise, to view the details of less than 10 channels, reduce the value of this parameter.

• If you want the test to report metrics for every channel on a node, then set the INDIVIDUAL CHANNELS flag to Yes. In this case, each channel will be a descriptor of this test. On the other hand, if you want to understand the overall message load across all channels and all nodes in a cluster, you can set this flag to No. In this case, the test will report metrics for a Summary descriptor alone.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.