both retention priority and recording priority storage retention modes. Under
retention priority, clients are required to manage the space available for
recordings because the system will not perform any automatic pruning. Under
recording priority, the system will automatically prune old recordings but the
pruning operation does not necessarily delete metadata or generated mp4 files
that were created using the deprecated convertSession API. MediaSense can be
configured to automatically clean up these elements or clients can take
proactive responsibility for managing their disk space.
recording priority, and you have not configured MediaSense to automatically
delete pruned metadata, the client application must actively delete sessions
that have been automatically pruned. Clients may either periodically issue an
API request for pruned sessions or they may elect to receive session pruned
events and explicitly delete those it no longer needs.
retention priority, there is no automatic pruning and the client is fully
responsible for guaranteeing that enough disk space is available for new
Only if the system
is configured for recording priority and automatic deletion of pruned
recordings is turned on can the client avoid taking part in storage management.
management activities are invoked using the MediaSense API. (For more
information, see the
Developer Guide.) If pruning activities are going to be performed
regularly, schedule them for low-usage periods in order to minimize impact on