Commit or Roll Back Configuration Changes in Paragon Insights

In Paragon Insights, when you make changes to the configuration, you can perform the following operations:

Save
Save and Deploy
Delete
Delete and Deploy

These operations and their effect on the Paragon Insights ingest services are explained in Table 1.

For changes that were not already deployed, you can either commit or roll back the changes, which you can do using the Health Configuration Deployment Status page; the procedure is provided below Table 1.

Table 1: Operations After Changing the Configuration in Paragon Insights
Operation	Explanation	Effect on Ingest Services
Save	Saves the changes to the database, but doesn't apply the changes to the ingest services.	No effect until the changes are committed.
Delete	Deletes the changes from the database, but doesn't apply the changes to the ingest services.	No effect until the changes are committed.
Save and Deploy	Saves the changes to the database and applies the changes to the ingest services.	When you commit a configuration, the changes are accepted after validation and acknowledged immediately. A background job tracks these changes to ingest services. The background job runs periodically and applies the changes to ingest services. Only after the background job applies these changes, does the ingest service process data based on the changes configured.
Delete and Deploy	Deletes the changes from the database and applies the changes to the ingest services.

Note:

Users might perform the Save or Delete operations if they have multiple configuration steps and want to stack the configuration steps, and commit the changes later at one go.

To commit or roll back configuration changes in Paragon Insights:

On the Paragon Automation banner, click the deployment status icon.
The Health Configuration Deployment Status page appears displaying:
- The status of the last deployment.
- The list of device groups and network groups for which pending changes are not yet committed.
- The list of device groups and network groups for which pending deletions are not yet committed.
You can do one of the following:
- Commit any changes that are pending deployment:
  1. Click Commit.
    
    Paragon Insights triggers the commit operation and the configuration changes are applied to the ingest services. Depending on the number of configuration changes and number of device groups and network groups affected, applying the configuration changes to the ingest services might take between a few seconds or a few minutes to complete.
    
    After the operation completes, a confirmation message appears. Paragon Insights starts running the associated playbooks and starts ingesting the data.
  2. Go to Step 3.
- Roll back any changes that are pending deployment:
  1. Click Rollback to roll back any changes that are pending deployment. (The roll back operation discards the pending configuration changes that were previously saved in the database.)
    
    Paragon Insights triggers the roll back operation and the configuration changes are rolled back almost immediately. After the rollback is complete, a confirmation message is displayed.
  2. Go to Step 3.
Note:
After the roll back or commit operation completes, the status of the last deployment in the Health Configuration Deployment Status page displays the last operation that was completed.
Click Close to exit the page.

You are returned to the previous page from which you accessed the Health Configuration Deployment Status page.

Commit or Roll Back Configuration Changes in Paragon Insights

Related Documentation