Persistence paths determine where policy results (good records, bad records, drift output, anomaly metrics) are stored. These locations typically point to S3, ADLS, or GCS.
Users configure persistence paths to:
- Retain error records for debugging
- Store drift profiles or anomaly metrics
- Archive execution results
- Feed external monitoring/analytics systems
Available Endpoints
| Action | Endpoint |
|---|---|
| Get Persistence Configuration | GET /catalog-server/api/rules/persistence/:assetId |
| Update Persistence Configuration | PUT /catalog-server/api/rules/persistence/:assetId |
Was this page helpful?