Hello Tim, I can help you with this. Can I have a measurement id where this issue happened? After how much time do you disconnect from the streaming?
Maybe you can drop on my email a snippet of code. Ciao, Massimo > On 14 Mar 2018, at 14:01, Tim Wattenberg <[email protected]> wrote: > > 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 > <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 > [email protected] <mailto:[email protected]> > +49 1578 8248731
