Accidentally deployed MCS profiles and now I don't see metrics in OC
search cancel

Accidentally deployed MCS profiles and now I don't see metrics in OC

book

Article ID: 422703

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You are using probe configuration via IM and superpackages and have accidentally deployed MCS profiles to many robots. 

Now metrics are not being sent anymore by the robots. 

How can we fix the issue and revert the change? 

Environment

DX UIM 23.4.5 and later

Cause

Accidentally deployed MCS profiles to Already existing configuration.

As per the kB Mixed configuration: configuring monitoring with MCS and IM / Admin Console GUI mixed configuration is not supported. 

So if MCS is used on top of existing configuration it can lead to unexpected results. 

Resolution

To resolve the issue and if only IM Based configuration is intended to be deployed for a particular probe: 

 

1. Delete any previously created MCS profiles and wait for the deletion cycle to complete (it might take some time until all profiles are deleted and all plugin_metric.cfg in each robot) is updated and metrics and policies are removed. 

2. When MCS profile is removed, the configuration is not reverted back to the previous stage but a default configuration is left. So in case of accidentally MCS profile deployment the previous configuration must be manually deployed to the target robots. (eg. redeploy the superpackages accordingly). 

 

Additional Information

NOTE: It is recommended to have DX UIM upgraded at least to 23.4.4 for better MCS performance and outcome. In 23.4.4 and later, MCS works better for deployments and for scenarios like the one described where profiles are deleted.