How to modify the retention period for Service Discovery objects moving to a "Not Existing" state in Aria Operations

Products

• VCF Operations

Issue/Introduction

This article provides instructions for modifying the default retention period for "Not Collecting" Service Discovery (SDMP) objects. By adjusting this configuration, administrators can control how objects transition from a "No Data Receiving" status to a "Not Existing" state within Aria Operations.

Environment

Aria Operations 8.18.x

Resolution

To reduce the time required to move objects into a "Not Existing" state, you will need to modify the Service Discovery adapter configuration. Follow these steps:

1. Open an SSH session to the Aria Operations Primary node.
   
   
2. Navigate to the following directory by running the command  cd  /usr/lib/vmware-vcops/user/plugins/inbound/ServiceDiscoveryAdapter3/conf/
   
   
3. Open the servicediscovery.properties file using a text editor (such as vi or nano).
   
   
4. Add or modify the following property, changing the value to your preferred duration in minutes: SERVICES_NUMBER_OF_MINUTES_TO_PUT_INTO_NOT_EXISTING_STATE=<desired_value> (Note: The default value is 10080 minutes, which equates to 7 days).
   
   
5. Save your changes and close the file.
   
   
6. To apply and synchronize the changes across your environment, restart the collector services in the following order:
• Step A: Restart the collector service on the Primary node by running the following command: service collector restart
• Step B: Restart the collector service on all non-primary cluster nodes using the same command. This allows them to fetch the updated configuration file from the primary node.
• Step C: Wait at least 60 seconds to ensure the configuration synchronization is fully completed across all non-primary nodes.
• Step D: Finally, restart the collector service on all Cloud Proxy nodes by running: service collector restart

 

Note: Please keep the following in mind before proceeding:

• Service Interruption: Restarting the collector service will cause a brief interruption (a few minutes) in data collection for any adapters assigned to those respective nodes.

• Product Upgrades: Manual modifications to configuration files are not persistent across product updates. These settings will revert to their default values following an Aria Operations upgrade. Ensure you document these changes internally so you can easily reapply them after any future upgrades.

Additional Information

• Cloud Proxies automatically synchronize their adapter configuration files from the primary node during the restart process. Rather than modifying each proxy individually, you only need to apply these changes to the primary node. Once updated, you can restart the collector service on your Cloud Proxies at your convenience, and they will automatically pull the new configuration.
• Any new Cloud Proxies deployed after the changes are made to the primary node will automatically inherit the updated settings.