Request storage and retention¶
UbiOps can store the data of requests made to deployments and pipelines, both for direct requests and for batch requests.
The data that can be stored for a request consists of two elements:
- Request metadata: the metadata is all information related to a request, except the data sent as input or produced as output. Specifically, metadata includes the creation and completion times of a request, its status, whether it was successful and who created it.
- Request input and output: the data that is sent as input or produced as output.
What data is stored and for how long can be configured for each deployment or pipeline version separately. The following settings are available:
- The request retention mode. The retention mode determines what data is stored for each request. There are three possible values:
- Full: everything is stored, both metadata and input and output.
- Metadata: only the metadata is stored.
- None: nothing is stored.
- The request retention time. The time for which the request data of request is stored after completion. It is automatically deleted within an hour after this time expires.
These settings can be configured in the WebApp or via the API when creating or editing a deployment or pipeline version. Changing the retention time or mode does not influence the retention of already stored requests.
Enabling request storage does not influence the response times of your deployment or pipeline, as the data is stored asynchronously. This does mean that it can take a couple of seconds for a request to become visible in the WebApp or API after it completes.
UbiOps does not retain any data of requests that have retention mode none or that are deleted, except for possible logs and metrics generated by the request.
Retention mode of deployments in pipelines
The retention mode configured for deployments applies to the deployment requests that are made as part of a pipeline request as well.
Request storage and batch requests¶
The retention settings apply to both direct and batch requests. Therefore, if you want to collect the result of batch requests when they are completed, you have to configure the retention mode to full with at least a 1 hour retention time.
Retention mode none or metadata for batch requests
For batch requests, the metadata and input data is always stored for the duration of the request, even if the retention mode of the deployment or pipeline version is set to none or metadata. This is required for the UbiOps platform to be able to process a batch request. The request is automatically deleted when the batch request completes.