Streaming result data missing probe information with "enrichProbes: true"
Hi folks, When using the Streaming API there is an option called "enrichProbes" which should cause probe metadata to be added to every result. That seems to have worked for a while, but it has stopped working. Example code (in python) to reproduce (it's the example from the docs, with just enrichProbes set to true): import json import websocket ws = websocket.WebSocket() ws.connect("wss://atlas-stream.ripe.net/stream/") params = {"streamType": "result", "msm": 1001, "enrichProbes": True} ws.send(json.dumps(["atlas_subscribe", params])) for data in ws: print(data) Example result: ["atlas_result",{"fw":5080,"mver":"2.6.2","lts":66,"dst_name":"193.0.14.129","af":4,"dst_addr":"193.0.14.129","src_addr":"192.168.1.20","proto":"ICMP","ttl":56,"size":32,"result":[{"rtt":21.447667},{"rtt":21.226292},{"rtt":21.253375}],"dup":0,"rcvd":3,"sent":3,"min":21.226292,"max":21.447667,"avg":21.3091113333,"msm_id":1001,"prb_id":50274,"timestamp":1731917452,"msm_name":"Ping","from":"85.107.81.62","type":"ping","step":240}] As you can see there is no probe metadata present. I'm fairly sure I'm doing this right and I think this worked previously. Is something broken in the backend? Best regards, Wouter
Hi Wouter, It looks like the backend is failing to retrieve the probe info, so it's not including it when enrichProbes is specified. We're looking into it now, I'll update here when we have a fix. Cheers, Chris On Mon, 18 Nov 2024 at 09:13, Wouter de Vries via ripe-atlas < ripe-atlas@ripe.net> wrote:
Hi folks,
When using the Streaming API there is an option called "enrichProbes" which should cause probe metadata to be added to every result. That seems to have worked for a while, but it has stopped working.
Example code (in python) to reproduce (it's the example from the docs, with just enrichProbes set to true):
import json import websocket
ws = websocket.WebSocket() ws.connect("wss://atlas-stream.ripe.net/stream/") params = {"streamType": "result", "msm": 1001, "enrichProbes": True} ws.send(json.dumps(["atlas_subscribe", params])) for data in ws: print(data)
Example result:
["atlas_result",{"fw":5080,"mver":"2.6.2","lts":66,"dst_name":"193.0.14.129","af":4,"dst_addr":"193.0.14.129","src_addr":"192.168.1.20","proto":"ICMP","ttl":56,"size":32,"result":[{"rtt":21.447667},{"rtt":21.226292},{"rtt":21.253375}],"dup":0,"rcvd":3,"sent":3,"min":21.226292,"max":21.447667,"avg":21.3091113333,"msm_id":1001,"prb_id":50274,"timestamp":1731917452,"msm_name":"Ping","from":"85.107.81.62","type":"ping","step":240}]
As you can see there is no probe metadata present.
I'm fairly sure I'm doing this right and I think this worked previously. Is something broken in the backend?
Best regards,
Wouter ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
This issue has now been resolved, enrichProbes should enable the full "probe" block once more. Chris On Tue, 26 Nov 2024 at 13:07, Christopher Amin <camin@ripe.net> wrote:
Hi Wouter,
It looks like the backend is failing to retrieve the probe info, so it's not including it when enrichProbes is specified. We're looking into it now, I'll update here when we have a fix.
Cheers, Chris
On Mon, 18 Nov 2024 at 09:13, Wouter de Vries via ripe-atlas < ripe-atlas@ripe.net> wrote:
Hi folks,
When using the Streaming API there is an option called "enrichProbes" which should cause probe metadata to be added to every result. That seems to have worked for a while, but it has stopped working.
Example code (in python) to reproduce (it's the example from the docs, with just enrichProbes set to true):
import json import websocket
ws = websocket.WebSocket() ws.connect("wss://atlas-stream.ripe.net/stream/") params = {"streamType": "result", "msm": 1001, "enrichProbes": True} ws.send(json.dumps(["atlas_subscribe", params])) for data in ws: print(data)
Example result:
["atlas_result",{"fw":5080,"mver":"2.6.2","lts":66,"dst_name":"193.0.14.129","af":4,"dst_addr":"193.0.14.129","src_addr":"192.168.1.20","proto":"ICMP","ttl":56,"size":32,"result":[{"rtt":21.447667},{"rtt":21.226292},{"rtt":21.253375}],"dup":0,"rcvd":3,"sent":3,"min":21.226292,"max":21.447667,"avg":21.3091113333,"msm_id":1001,"prb_id":50274,"timestamp":1731917452,"msm_name":"Ping","from":"85.107.81.62","type":"ping","step":240}]
As you can see there is no probe metadata present.
I'm fairly sure I'm doing this right and I think this worked previously. Is something broken in the backend?
Best regards,
Wouter ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
participants (2)
-
Christopher Amin -
Wouter de Vries