[atlas] Streaming API Losses

Hi all,

We've been exploring the use of the Streaming API to collect result stream
data for a set of user defined measurements, in particular using the
interface available in Cousteau.

However, we've found that the Streaming API seems to be "lossy", with only
a fraction of the results reported through the usual system making their
way into the stream. I've not been able to find any sort of pattern on what
does and doesn't make it through.

Does anyone else have experience with this? Are there known limitations
with the Streaming API? If so, has anyone worked out any clever workflows
to accommodate?

Thanks very much!

-- 
*Marcel Flores, PhD* | Sr. Research Scientist
research.verizondigitalmedia.com | AS15133
<https://www.peeringdb.com/asn/15133>
p: +1 310.593.6880 e: marcel.flores at verizondigitalmedia.com
13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20190628/1b615bd5/attachment.html>