Solved: Media Sense Get Pruned Data

ackarabas · ‎11-09-2015

Hello,

I got stuck about one issue. In media Sense search and play, We couldn't look the recordings which is older than 60 days.

I have realized, Prune conf is 60 days, but we don't delete older logs.

I have researched then I found that these data named Pruned Data.

Could you please help me how I can get these datas?

Regards..

Deepak Rawat · ‎11-10-2015

Please find the information below regarding the Prune Policy Configuration:

The MediaSense SRND under the section "Proactive Storage Management":

MediaSense offers 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. When using 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.

Another way to look at this is that "pruned" sessions are not the same thing as "deleted" sessions:

Pruned sessions have been marked for removal by an algorithm in the MediaSense system. No person was involved in the decision to prune these sessions. So even though these sessions are moved to the "DELETED" state, these sessions are NOT actually removed from the metadata. Human (or Application) intervention is required. Because these sessions are in the "DELETED" state, these sessions are not visible to most queries. However, these sessions ARE visible to the "getAllPrunedSessions" query API. Also, if any mp4 files were generated for these sessions, these mp4 files continue to be present on the disk and continue to be available for download until the pruned sessions are actually DELETED.

If you select the First option(Automatically Remove data and recording), After Pruning, Recording's data and MP4 files will be removed automatically from Mediasense server. So, these recordings (data and MP4 file) can't be accessed by any way from Mediasense server.

If you select the second option (Do Not Automatically ...), then, Mp4 files are generated once you play them or download them and they get aged out after every 2 hrs. It will remain at the specific location for 2 hrs after that you again have to use the api to play or download it and data associated with session will always be in database.

Below are the documentation links that contains everything you should be knowing about Pruning along with a good discussion around this at the MediaSense Community:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/Design_Guide/CUMS_BK_MC36D963_00_mediasense-srnd_11.pdf

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/User_Guide/CUMS_BK_M5B01864_00_ms-user-guide-11.pdf

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/Developer_Guide/CUMS_BK_ms-dev-guide-11.pdf

https://communities.cisco.com/message/170529#170529

https://communities.cisco.com/docs/DOC-48816

Regards

Deepak

- Rate Helpful Posts -

View solution in original post

Deepak Rawat · ‎11-10-2015

Please find the information below regarding the Prune Policy Configuration:

The MediaSense SRND under the section "Proactive Storage Management":

MediaSense offers 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. When using 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.

Another way to look at this is that "pruned" sessions are not the same thing as "deleted" sessions:

Pruned sessions have been marked for removal by an algorithm in the MediaSense system. No person was involved in the decision to prune these sessions. So even though these sessions are moved to the "DELETED" state, these sessions are NOT actually removed from the metadata. Human (or Application) intervention is required. Because these sessions are in the "DELETED" state, these sessions are not visible to most queries. However, these sessions ARE visible to the "getAllPrunedSessions" query API. Also, if any mp4 files were generated for these sessions, these mp4 files continue to be present on the disk and continue to be available for download until the pruned sessions are actually DELETED.

If you select the First option(Automatically Remove data and recording), After Pruning, Recording's data and MP4 files will be removed automatically from Mediasense server. So, these recordings (data and MP4 file) can't be accessed by any way from Mediasense server.

If you select the second option (Do Not Automatically ...), then, Mp4 files are generated once you play them or download them and they get aged out after every 2 hrs. It will remain at the specific location for 2 hrs after that you again have to use the api to play or download it and data associated with session will always be in database.