Determining of lifespan-expired for samples at writer side

1 post / 0 new
Log in or register to post comments
Tue, 10/28/2014 - 05:27
#1
davidoh
Offline
Last seen: 9 years 3 months ago
Joined: 05/25/2014
Posts: 6
Determining of lifespan-expired for samples at writer side

Hello,

I have a reliable writer configured with:
lifespan QOS of 60 sec.
history size: 30000, keep last

 

The transport is low bandwidth, and on peak situations samples may be produced at higher rate than network capacity.

I would like to be able to log any sample (by the sample's ID field), in case the writer had to drop it before sending, due to expired lifespan.

Is this possible via writer listener callback or some other machanism ?

Also, is it possible to get notfied on situation when a sample is overwritten in the writer's queue before is was sent on the wire (due to cache full)?

Thanks

David

Organization:
Top