This is a workaround to disable the dashboard_engine temp queues, and get the information in a more efficient method. This describes how to avoid any adverse performance impact on the hub from unnecessary dashboard_engine temp queues.
Restarting the dashboard_engine temporarily relieves the issue but the temp queue(s) will start to build again. The basic problem is "too much QoS". This is a workaround to disable the temp queues, and get the information in a more efficient method.
In large environments using nis_server, it is possible for the volume of QoS measurements to overwhelm the hub, causing constant QoS message queues to form. If this occurs, the hub's performance may not be optimal. In addition, the summary lists in the Dynamic Views portlet in UMP may not display up-to-date QoS data.
As an option, you can disable dashboard_engine 'QoS listening' to reduce the hub's workload.
Note: Disabling QoS listening results in a number of empty columns in the Summary views in Dynamic Views. The dashboard_engine's functionality is not affected in other UMP portlets, such as Alarm Console, Custom Dashboards, and Dynamic View Dashboards. This procedure includes an optional
step to fix the empty columns that result in the Summary views.
To disable QoS listening, follow these steps:
- Locate and select the dashboard_engine probe in Infrastructure Manager.
- Press the <Ctrl> key as you right-click on the dashboard_engine, and then select Raw Configure.
- With the data section highlighted, locate the qos_subscription_enabled key, and click Edit Key. If the qos_subscription_enabled key does not appear, click New Key, and add qos_subscription_enabled.
- Enter 0 for the value of the qos_subscription_enabled key.
When you click OK, the dashboard_engine probe restarts. You can verify that your changes took effect by checking the dashboard_engine.log, which will show the following message on level 2:
NIS server is still used, but QoS hub subscription is disabled.
- Configure the data_engine to provide dashboard_engine with QoS data. (optional)
Note: This step is optional
, and is a workaround for the empty columns that result in the Summary views in Dynamic Views.
- In the data_engine probe, locate the setup section:
- Edit ?update_last_value? to yes.
- Make note of the value that lsv_sleep is set to. The lsv_sleep key determines the interval, in seconds, between each batch update data_engine makes to the S_QOS_SNAPSHOT table.
- Restart the data_engine probe.
- On the dashboard_engine:
- In the updateintervals section, add the key ?qos_data_update_interval.?
- Set ?qos_data_update_interval? to a non-zero value in seconds. For example, enter 60.
- Ensure that the ?qos_data_update_interval? is set to the same or higher value as both the ?lsv_sleep? and the ?update_ums_interval.?
To confirm the problem is resolved after the settings have been changed and applied, open the hub probe and select the Status tab and check the dashboard_engine queues. Check the ID column under hub Subscribers/Queues for the relevant probe/client program, in this case the dashboard_engine.