On 18/07/2012 11:51, Roman Mamedov wrote:

On Wed, 18 Jul 2012 09:38:22 +0200 kix <kix@kix.es> wrote:

...

In this new article on RIPE Labs we present a first experimental analysis and a prototype visualisation of the traceroute results:

https://labs.ripe.net/Members/emileaben/visualise-your-ipv6-connectivity-usi...

...

So I was interested by this and went and created my first UDM. I have chosen "traceroute" and did not mark the "Do not visualise" checkbox. However in the Results section I now see only a table in an obscure format, and an option to "Download as JSON". How do I get some kind of visualisation of these results?

Is that something only for LIRs? Well, even not asking for the pretty graphs, how do I view traceroutes as regular plaintext traceroutes shown on a web page, not a machine-readable structure? Note: please do not suggest to write my own JSON processing to merely view a traceroute.

Hi Roman, We are experimenting with how to visualize large amounts of traceroutes. In the Labs article you mention I wrote about how this is done for the IPv6 traceroutes that were done through the LIR-only interface for this at: https://atlas.ripe.net/atlas/ipv6_traces.html So that is currently only available for these measurements. An example of the visualization for ns.ripe.net can be found here: http://albatross.ripe.net/cgi-bin/demo-area/v6reach.cgi?msm_id=1002799;nonce... For other traceroute measurements there are no other results currently other then the JSON-downloads and the table with unformatted JSON results. Having that available as something plain-text to read (for when you have small amounts of traceroute data), is a good suggestion I think. best regards, Emile Aben RIPE NCC

Am 18.07.2012 15:14:19, schrieb Leo Bicknell:

I've had to deal with JSON before, but it was long ago and far away. I suspect it is not something most sysadmin/netadmin types deal with on a daily basis. It's not hard, just not familar.

To that end, if RIPE could produce a template/example in a few popular languages (perl, python, ruby, php) to download the JSON and parse into the native language data structure that could get a LOT more folks using the data...

Javascript: At https://www.bartschnet.de/lib/js/XMLHttpRequest.js you can find my Javascript-function which I use to directly communicate with a JSON-API via POST from a browser. url:         API-URL object:    Javascript-object to be converted to JSON and sent to API ( can be "{}") if you don't want to send any data callback: Javascript-function which gets a javascript-object converted from JSON-POST-result as only parameter PHP: You can directly decode JSON to PHP-objects/arrays with: http://php.net/manual/en/function.json-decode.php or encode any PHP data type including objects and arrays to JSON with: http://php.net/manual/en/function.json-encode.php Just do not forget JSON-strings are UTF-8! Best regards, Renne -- Sent with love from the new tine 2.0 email client ... Please visit http://tine20.org

On 2012.07.18. 15:45, Matija Grabnar wrote:

On 07/18/2012 03:08 PM, Leo Bicknell wrote:

...

To that end, if RIPE could produce a template/example in a few popular languages (perl, python, ruby, php) to download the JSON and parse into the native language data structure that could get a LOT more folks using the data...

You can fins a bunch of decoders in more languages than I count on http://www.json.org/

Hi, It's really nice to see the community in action :-) It is a rather encouraging sign to us! To answer Leo's original question from a different perspective: the result data you get from Atlas is a structured piece of information. We had to choose a specific encoding, and we opted for JSON (as opposed to YAML, XML, etc.) because in many cases that can be directly used in client side applications. We *could* supply other formats too, but no matter what the encoding is, you need some kind of client library to parse it. Regards, Robert