SRM 4.10 :: Changing the "Performance polling period" value in the Solution Pack UI for VNX/Unity does not change the value in vnxe-realtime-performance.xml
Summary:
Changing the "Performance polling period" value in the Solution Pack UI does not change the value in vnxe-realtime-performance.xml. The configuration file has this setting hardcoded
for 5 minutes.
300s
in the file /opt/APG/Collecting/Stream-Collector/emc-vnx/conf/parsers/vnxe-realtime-performance.xml
...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Even after increasing the polling interval to 15 minutes or higher, VNX/Unity collecting logs showed real time performance data collection every 5 minutes
INFO -- [yyyy-mm-dd hh:37:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:37:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2608 msec
INFO -- [yyyy-mm-dd hh:42:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:42:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2816 msec
INFO -- [yyyy-mm-dd hh:47:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:47:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2627 msec
INFO -- [yyyy-mm-dd hh:52:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:52:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2654 msec
INFO -- [yyyy-mm-dd hh:57:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:57:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2598 msec
INFO -- [yyyy-mm-dd hh:37:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:37:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2608 msec
INFO -- [yyyy-mm-dd hh:42:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:42:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2816 msec
INFO -- [yyyy-mm-dd hh:47:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:47:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2627 msec
INFO -- [yyyy-mm-dd hh:52:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:52:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2654 msec
INFO -- [yyyy-mm-dd hh:57:32 EDT] -- Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname
INFO -- [yyyy-mm-dd hh:57:35 EDT] -- Collecting$CollectingJobHook::completingJob(): Completed collecting configuration VNXUNITY-REALTIME-PERFORMANCE for context UNITY-unityname in 2598 msec
Cause
None
Resolution
This is working as designed. The real time performance collection interval in SRM is hardcoded to 5 minutes and does not change with the performance polling interval change. This is due to a VNX/Unity REST API limitation. The REST API for fetching real-time metrics works with polling interval of maximum 5 minutes.
Article Properties
Article Number: 000218620
Article Type: Solution
Last Modified: 13 Nov 2023
Version: 2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.