ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to cleanup SelfMonitoring Data in SOI 4.2 CU3

book

Article ID: 238876

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

How to clean up or remove all data that is generated when Selfmonitoring is activated using Selfmonitoring SOI 4.2 CU3 Manager configuration. 

 

 

Cause

Data removal 

Environment

Release : SOI 4.2 CU3

Component : Selfmonitoring 

Resolution

SelfMonitoring uses Universal Connector to collect and publish, so user may use “cleanImportedData” option in Soitoolbox command.

 Ex:  soitoolbox --machine=<DB Host> --dbName=SAMStore --dbUsername=sa --dbPassword=<sa password> --cleanImportedData --connector="CA:09997_addbr01-I2xx0.ca.com"

Note:

it removes all Universal Connector data along with Selfmonitoring.

 

 

Additional Information

This is the out-of-the-box solution available to clean up universal connector data (which includes self-monitoring data). But if the user does not wish to delete all the data then there is no out-of-the-box solution to clean up only the self-monitoring alerts. 
 
One thing the user can try is to clear inactive alerts by running the purgeClearedAlerts this might help because the self-monitoring alerts will be auto cleared whenever the services are back to normal. Please note that other data like Services will still remain.
Check this community for similar discussion