[atlas] Result streaming lacking results
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] Result streaming lacking results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Wattenberg
mail at timwattenberg.de
Wed Mar 14 14:01:58 CET 2018
Hi everyone, I'm working on a project where I create a measurement via API and immediately subscribe to the result stream as well as the metadata stream ( https://atlas.ripe.net/docs/api/v2/manual/measurements/result-streaming.html ). socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, sendBacklog: true}); socket.emit("atlas_subscribe", {stream_type: "metadata", msm: mid}); Now even with (and also without) the sendBacklog option enabled, I rarely get even close to receive all results (the measurement produces max. 10 in total, I received max. 4-5, often only one or even none). Same goes for metadata, where I sometimes get the action: creation event, but never a notification when the measurement is stopped. Another question in this context: When does a one-off measurement gets stopped? I also subscribed to (dis)connect, atlas_error and atlas_subscribed but they give no hint what could be going wrong. I also tried the replay feature, which did not work at all for me either: socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, startTime: <Time of creation>}); What am I doing wrong? Thanks, Tim Tim Wattenberg mail at timwattenberg.de +49 1578 8248731 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20180314/2f7c228e/attachment.html>
- Previous message (by thread): [atlas] API Keys problem?
- Next message (by thread): [atlas] Result streaming lacking results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]