Archive and purge using UI
The ability to purge and archive logging and monitoring data is critical to data housekeeping. API Gateway provides an integrated framework for archiving and purging the logging and monitoring data. By archiving and purging data from the API Gateway database, you can maintain a healthy and optimal API Gateway database, as well as keep your data archived for future use.
Note:
The Archive or Purge operations are carried out on the API Data Store. If you use an external Elasticsearch as a Data store for API Gateway, the archive or purge operations are performed against that data store. These operations do not work on the data stores that are configured as destinations for transactions & logs.
The following data can be archived or purged using Archive & Purge in API Gateway database:
Audit logs. Archives and purges the auditable event data.
Error events. Archives and purges the runtime error event data.
Lifecycle events. Archives and purges the
API Gateway's lifecycle data.
Monitor events. Archives and purges the runtime monitoring data.
Performance metrics. Archives and purges the runtime performance metrics data.
Policy violation events. Archives and purges the policy compliance violation data.
Threat protection events. Archives and purges the threat protection data.
Transaction events. Archives and purges the API transactional data.
Application logs. Archives and purges the aggregated logs.
Mediator trace span. Archives and purges the stage-wise trace data.
Server log trace. Archives and purges the server log data.
Request response trace. Archives and purges the aggregated request and response trace data.