This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] Streaming API Losses
- Previous message (by thread): [atlas] Filter for all results of a probe within a given timeintervall
- Next message (by thread): [atlas] Search for Probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcel Flores
marcel.flores at verizondigitalmedia.com
Fri Jun 28 20:56:02 CEST 2019
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: </ripe/mail/archives/ripe-atlas/attachments/20190628/1b615bd5/attachment.html>
- Previous message (by thread): [atlas] Filter for all results of a probe within a given timeintervall
- Next message (by thread): [atlas] Search for Probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]