From colin at spakka.net Fri Mar 2 11:56:26 2018 From: colin at spakka.net (Colin Petrie) Date: Fri, 2 Mar 2018 18:56:26 +0800 Subject: [atlas] ipv6 v1 probe test how In-Reply-To: References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: Your probe page: https://atlas.ripe.net/probes/2317/ Says you have tags: IPv6 Works IPv6 Capable IPv6 Stable 1day Sounds like it is already working :) Cheers, Colin (a different one) On 19/02/2018 21:39, Colin Johnston wrote: > How does one test ipv6 on my v1 probe > I have bt homehub6 so ipv6 enabled now :) > > probe id 2317 > > Firmware > 4790 > > Architecture > probev1 > > Colin > From md1clv at md1clv.com Thu Mar 8 18:27:13 2018 From: md1clv at md1clv.com (Daniel Ankers) Date: Thu, 8 Mar 2018 17:27:13 +0000 Subject: [atlas] API Keys problem? Message-ID: Hi, Has there been a change in the way that API keys work for the measurement results API? I've got an API key which is granted permission to get results from a non-public measurement. When I do: curl -H "Authorization: Key $KEY" " https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start= 1520510400" (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get: {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}} This was previously working, but I'm not sure exactly when it stopped. I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned. Regards, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From gponikie at akamai.com Thu Mar 8 18:30:06 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Thu, 8 Mar 2018 17:30:06 +0000 Subject: [atlas] API Keys problem? In-Reply-To: References: Message-ID: Hi! I had the same issue 28th Feb. I had to add 'probes - Get non-public measurement results' to my API key to fix it. Regards, Grzegorz From: Daniel Ankers Date: Thursday 2018-03-08 at 18:27 To: "ripe-atlas at ripe.net" Subject: [atlas] API Keys problem? Hi, Has there been a change in the way that API keys work for the measurement results API? I've got an API key which is granted permission to get results from a non-public measurement. When I do: curl -H "Authorization: Key $KEY" "https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=1520510400" (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get: {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}} This was previously working, but I'm not sure exactly when it stopped. I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned. Regards, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel.flores at verizondigitalmedia.com Thu Mar 8 18:33:55 2018 From: marcel.flores at verizondigitalmedia.com (Marcel Flores) Date: Thu, 8 Mar 2018 09:33:55 -0800 Subject: [atlas] API Keys problem? In-Reply-To: References: Message-ID: We had a similar issue on 28th Feb -- though I think our error was that there were no grants on the key (it had been working for months, showed fine on the UI). I just made a new key and had no issue after. -m On Thu, Mar 8, 2018 at 9:30 AM, Ponikierski, Grzegorz wrote: > Hi! > > > > I had the same issue 28th Feb. I had to add 'probes - Get non-public > measurement results' to my API key to fix it. > > > > Regards, > > Grzegorz > > > > *From: *Daniel Ankers > *Date: *Thursday 2018-03-08 at 18:27 > *To: *"ripe-atlas at ripe.net" > *Subject: *[atlas] API Keys problem? > > > > Hi, > > Has there been a change in the way that API keys work for the measurement > results API? > > > > I've got an API key which is granted permission to get results from a > non-public measurement. When I do: > > > > curl -H "Authorization: Key $KEY" "https://atlas.ripe.net/api/ > v2/measurements/$MEASUREMENT/results/?start= > > 1520510400" > > > > (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I > get: > > > > {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your > keys has no grants"}],"code":102,"detail":"There was a problem with your > request","title":"Bad Request"}} > > > > > > This was previously working, but I'm not sure exactly when it stopped. > I've checked that getting the data through my browser works while I'm > logged into the site, and that if I request https://atlas.ripe. > net/api/v2/measurements/$MEASUREMENT/latest > > using the API key I get data returned. > > > > Regards, > > Dan > -- *Marcel Flores, PhD* | Research Scientist VerizonDigitalMedia.com | AS15133 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: From md1clv at md1clv.com Thu Mar 8 18:36:53 2018 From: md1clv at md1clv.com (Daniel Ankers) Date: Thu, 8 Mar 2018 17:36:53 +0000 Subject: [atlas] API Keys problem? In-Reply-To: References: Message-ID: Hi Grzegorz, "probes - Get non-public measurement results" is exactly what was needed - thank you! Regards, Dan On 8 March 2018 at 17:30, Ponikierski, Grzegorz wrote: > Hi! > > > > I had the same issue 28th Feb. I had to add 'probes - Get non-public > measurement results' to my API key to fix it. > > > > Regards, > > Grzegorz > > > > *From: *Daniel Ankers > *Date: *Thursday 2018-03-08 at 18:27 > *To: *"ripe-atlas at ripe.net" > *Subject: *[atlas] API Keys problem? > > > > Hi, > > Has there been a change in the way that API keys work for the measurement > results API? > > > > I've got an API key which is granted permission to get results from a > non-public measurement. When I do: > > > > curl -H "Authorization: Key $KEY" "https://atlas.ripe.net/api/ > v2/measurements/$MEASUREMENT/results/?start= > > 1520510400" > > > > (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I > get: > > > > {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your > keys has no grants"}],"code":102,"detail":"There was a problem with your > request","title":"Bad Request"}} > > > > > > This was previously working, but I'm not sure exactly when it stopped. > I've checked that getting the data through my browser works while I'm > logged into the site, and that if I request https://atlas.ripe. > net/api/v2/measurements/$MEASUREMENT/latest > > using the API key I get data returned. > > > > Regards, > > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gponikie at akamai.com Thu Mar 8 18:40:23 2018 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Thu, 8 Mar 2018 17:40:23 +0000 Subject: [atlas] API Keys problem? In-Reply-To: References: Message-ID: <59486CA3-3C84-434C-8FF8-8B9D1149E4A8@akamai.com> Glad to hear that :) It was strange to me because I already had 'measurements - Get results from a non-public measurements' which worked fine. So now I have: 'measurements - Get results from a non-public measurements' 'probes - Get non-public measurement results' It looks quite redundant for me but it works :) Regards, Grzegorz From: Daniel Ankers Date: Thursday 2018-03-08 at 18:36 To: "Ponikierski, Grzegorz" Cc: "ripe-atlas at ripe.net" Subject: Re: [atlas] API Keys problem? Hi Grzegorz, "probes - Get non-public measurement results" is exactly what was needed - thank you! Regards, Dan On 8 March 2018 at 17:30, Ponikierski, Grzegorz > wrote: Hi! I had the same issue 28th Feb. I had to add 'probes - Get non-public measurement results' to my API key to fix it. Regards, Grzegorz From: Daniel Ankers > Date: Thursday 2018-03-08 at 18:27 To: "ripe-atlas at ripe.net" > Subject: [atlas] API Keys problem? Hi, Has there been a change in the way that API keys work for the measurement results API? I've got an API key which is granted permission to get results from a non-public measurement. When I do: curl -H "Authorization: Key $KEY" "https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=1520510400" (Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I get: {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your keys has no grants"}],"code":102,"detail":"There was a problem with your request","title":"Bad Request"}} This was previously working, but I'm not sure exactly when it stopped. I've checked that getting the data through my browser works while I'm logged into the site, and that if I request https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the API key I get data returned. Regards, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From vnaumov at ripe.net Fri Mar 9 09:49:30 2018 From: vnaumov at ripe.net (Viktor Naumov) Date: Fri, 9 Mar 2018 09:49:30 +0100 Subject: [atlas] API Keys problem? In-Reply-To: <59486CA3-3C84-434C-8FF8-8B9D1149E4A8@akamai.com> References: <59486CA3-3C84-434C-8FF8-8B9D1149E4A8@akamai.com> Message-ID: <1749c34c-d1f3-2bd5-6d7a-e385083e1a60@ripe.net> Hi, There was a bug allowing to get non-public built-in results from non-public probes. Therefore probes must be added to the key you want to get access to. Now it is fixed and lead to adding probes to 'probes - Get non-public measurement results' API key. Sorry for the hassle. wbr /vty On 3/8/18 6:40 PM, Ponikierski, Grzegorz wrote: > > Glad to hear that :) > > It was strange to me because I already had 'measurements - Get results > from a non-public measurements' which worked fine. So now I have: > > 'measurements - Get results from a non-public measurements' > > 'probes - Get non-public measurement results' > > It looks quite redundant for me but it works :) > > Regards, > > Grzegorz > > *From: *Daniel Ankers > *Date: *Thursday 2018-03-08 at 18:36 > *To: *"Ponikierski, Grzegorz" > *Cc: *"ripe-atlas at ripe.net" > *Subject: *Re: [atlas] API Keys problem? > > Hi Grzegorz, > > "probes - Get non-public measurement results" is exactly what was > needed - thank you! > > Regards, > > Dan > > On 8 March 2018 at 17:30, Ponikierski, Grzegorz > > wrote: > > Hi! > > I had the same issue 28^th Feb. I had to add 'probes - Get > non-public measurement results' to my API key to fix it. > > Regards, > > Grzegorz > > *From: *Daniel Ankers > > *Date: *Thursday 2018-03-08 at 18:27 > *To: *"ripe-atlas at ripe.net" > > > *Subject: *[atlas] API Keys problem? > > Hi, > > Has there been a change in the way that API keys work for the > measurement results API? > > I've got an API key which is granted permission to get results > from a non-public measurement.? When I do: > > curl -H "Authorization: Key $KEY" > "https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=1520510400" > > (Replacing $KEY with the key and $MEASUREMENT with the measurement > ID) I get: > > {"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your > keys has no grants"}],"code":102,"detail":"There was a problem > with your request","title":"Bad Request"}} > > This was previously working, but I'm not sure exactly when it > stopped.? I've checked that getting the data through my browser > works while I'm logged into the site, and that if I request > https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latestusing > the API key I get data returned. > > Regards, > > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at timwattenberg.de Wed Mar 14 14:01:58 2018 From: mail at timwattenberg.de (Tim Wattenberg) Date: Wed, 14 Mar 2018 14:01:58 +0100 Subject: [atlas] Result streaming lacking results Message-ID: 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: