[atlas]time base / synch for the "lst two hours" graphs?
I just noticed that the various graphs for the "last 2 hours" display seem to be based on different clocks or update cycles (delta = some 25m). Should these graphs be "synchronised"?
From a UI-perspective it would certainly be a bonus to have them aligned, at least for one probe.
All the best, Wilfried.
Hi Wilfried, We cannot display synchronized graphs at the last measurement time position because RRDs are updated only when the measurement data comes from the probe. Probes are allowed to send data not synchronous for all the measurements. As it implemented currently, we stop the graph at the time stamp of the last measurement. We can do it using current time, in this case graphs will be aligned, but unreceived data will be displayed as a gray area, that's what we do not really want. From your email I can guess that you are fetching graphs for your own page. In this case you can set the end time which ever you want: http://atlas.ripe.net/atlas/rrd.png?prb_id=3&msm_id=1001&type=minutely&*end=now* or even allow it to be, for example, 15 minutes older: http://atlas.ripe.net/atlas/rrd.png?prb_id=3&msm_id=1001&type=minutely&*end=now-15min* now is UTC Best regards, /vty On 03/30/2011 04:06 PM, Wilfried Woeber, UniVie/ACOnet wrote:
I just noticed that the various graphs for the "last 2 hours" display seem to be based on different clocks or update cycles (delta = some 25m).
Should these graphs be "synchronised"?
From a UI-perspective it would certainly be a bonus to have them aligned, at least for one probe.
All the best, Wilfried.
Hi Viktor, thanks for the explanation! Viktor Naoumov wrote:
Hi Wilfried,
We cannot display synchronized graphs at the last measurement time position because RRDs are updated only when the measurement data comes from the probe. Probes are allowed to send data not synchronous for all the measurements.
As it implemented currently, we stop the graph at the time stamp of the last measurement. We can do it using current time, in this case graphs will be aligned, but unreceived data will be displayed as a gray area, that's what we do not really want.
I agree :-)
From your email I can guess that you are fetching graphs for your own page.
No, not yet. I was looking at the various graphs in the pop-up tabs for my probe. Thus I noticed that the time periods for those graphs were different.
In this case you can set the end time which ever you want:
http://atlas.ripe.net/atlas/rrd.png?prb_id=3&msm_id=1001&type=minutely&*end=now*
OK, thanks for this. Is there a description somewhere? prb_id is obvious :-) but which valuess are valid for msm_id? I presume I can guess the values for type...
or even allow it to be, for example, 15 minutes older:
http://atlas.ripe.net/atlas/rrd.png?prb_id=3&msm_id=1001&type=minutely&*end=now-15min*
now is UTC
:-)
Best regards,
/vty
Thanks, best regards, Wilfried.
On 03/30/2011 04:06 PM, Wilfried Woeber, UniVie/ACOnet wrote:
I just noticed that the various graphs for the "last 2 hours" display seem to be based on different clocks or update cycles (delta = some 25m).
Should these graphs be "synchronised"?
From a UI-perspective it would certainly be a bonus to have them aligned, at least for one probe.
All the best, Wilfried.
On 03/30/2011 05:59 PM, Wilfried Woeber, UniVie/ACOnet wrote:
Hi Viktor,
thanks for the explanation! you're welcome OK, thanks for this. Is there a description somewhere? prb_id is obvious :-) but which valuess are valid for msm_id? I presume I can guess the values for type...
Here you go... msm_id you can find out in the web page source :) http:/atlas.ripe.net/atlas/rrd.png?prb_id=1&msm_id=2&type=daily&end=last .png - file type (can be .png, .svg, .eps, .pdf) List and description of GET arguments: prb_id - Probe ID msm_id - Measurement ID graph - graph name. Predefined collection of graphs currently 'tiny_rtt' and 'default'. If not defined - 'default' is assumed type - type of the graphs: 'minutely' : 'end-7200' - 'now' 'hourly' : 'end-28800' - 'now' 'daily' : 'end-90000' - 'now' 'weekly' : 'end-691200' - 'now' 'monthly' : 'end-2678400' - 'now' 'yearly' : 'end-31536000' - 'now' start - when graph should begin (see AT-STYLE TIME SPECIFICATION on RRD fetch page) end - when graph should end, same as start but also included keyword 'last', that end the graph at the last entered measurement 'start' and 'end' override 'type' width - width of the graph canvas in pixels (Title, legend, axis names are not included) height - canvas height in pixels (Title, legend, axis names are not included) Best regards, /vty
Please also note that RRD is just the current visualisation tool. We'd also like to give you access to "your data" -- ie. data collected by your probe so that you can do your own graphs if you want to. Regards, Robert On 2011.03.30. 22:24, Viktor Naoumov wrote:
On 03/30/2011 05:59 PM, Wilfried Woeber, UniVie/ACOnet wrote:
Hi Viktor,
thanks for the explanation! you're welcome OK, thanks for this. Is there a description somewhere? prb_id is obvious :-) but which valuess are valid for msm_id? I presume I can guess the values for type...
Here you go...
msm_id you can find out in the web page source :)
http:/atlas.ripe.net/atlas/rrd.png?prb_id=1&msm_id=2&type=daily&end=last
.png - file type (can be .png, .svg, .eps, .pdf)
List and description of GET arguments:
prb_id - Probe ID msm_id - Measurement ID graph - graph name. Predefined collection of graphs currently 'tiny_rtt' and 'default'. If not defined - 'default' is assumed type - type of the graphs: 'minutely' : 'end-7200' - 'now' 'hourly' : 'end-28800' - 'now' 'daily' : 'end-90000' - 'now' 'weekly' : 'end-691200' - 'now' 'monthly' : 'end-2678400' - 'now' 'yearly' : 'end-31536000' - 'now'
start - when graph should begin (see AT-STYLE TIME SPECIFICATION on RRD fetch page) end - when graph should end, same as start but also included keyword 'last', that end the graph at the last entered measurement 'start' and 'end' override 'type' width - width of the graph canvas in pixels (Title, legend, axis names are not included) height - canvas height in pixels (Title, legend, axis names are not included)
Best regards,
/vty
Viktor, fist of all thanks for the explanation of the control parameters! Being able to configure the plots is extremely helpful. There's one thing that I would like to do, if possible with your interface: I'd like to control the scaling of the Y-axis, in order to make graphs "optically comparable" on the spot. Is this possible? TIA Wilfried. Viktor Naoumov wrote:
On 03/30/2011 05:59 PM, Wilfried Woeber, UniVie/ACOnet wrote:
Hi Viktor,
thanks for the explanation!
you're welcome
OK, thanks for this. Is there a description somewhere? prb_id is obvious :-) but which valuess are valid for msm_id? I presume I can guess the values for type...
Here you go...
msm_id you can find out in the web page source :)
http:/atlas.ripe.net/atlas/rrd.png?prb_id=1&msm_id=2&type=daily&end=last
.png - file type (can be .png, .svg, .eps, .pdf)
List and description of GET arguments:
prb_id - Probe ID msm_id - Measurement ID graph - graph name. Predefined collection of graphs currently 'tiny_rtt' and 'default'. If not defined - 'default' is assumed type - type of the graphs: 'minutely' : 'end-7200' - 'now' 'hourly' : 'end-28800' - 'now' 'daily' : 'end-90000' - 'now' 'weekly' : 'end-691200' - 'now' 'monthly' : 'end-2678400' - 'now' 'yearly' : 'end-31536000' - 'now'
start - when graph should begin (see AT-STYLE TIME SPECIFICATION on RRD fetch page) end - when graph should end, same as start but also included keyword 'last', that end the graph at the last entered measurement 'start' and 'end' override 'type' width - width of the graph canvas in pixels (Title, legend, axis names are not included) height - canvas height in pixels (Title, legend, axis names are not included)
Best regards,
/vty
Hi Wilfried, It's not possible at the moment. See Robert's email about access to your data, so you can build graph yourself. WBR /vty On 04/08/2011 09:23 PM, Wilfried Woeber, UniVie/ACOnet wrote:
Viktor,
fist of all thanks for the explanation of the control parameters! Being able to configure the plots is extremely helpful.
There's one thing that I would like to do, if possible with your interface: I'd like to control the scaling of the Y-axis, in order to make graphs "optically comparable" on the spot. Is this possible?
TIA Wilfried.
Viktor Naoumov wrote:
On 03/30/2011 05:59 PM, Wilfried Woeber, UniVie/ACOnet wrote:
Hi Viktor,
thanks for the explanation! you're welcome
OK, thanks for this. Is there a description somewhere? prb_id is obvious :-) but which valuess are valid for msm_id? I presume I can guess the values for type...
Here you go...
msm_id you can find out in the web page source :)
http:/atlas.ripe.net/atlas/rrd.png?prb_id=1&msm_id=2&type=daily&end=last
.png - file type (can be .png, .svg, .eps, .pdf)
List and description of GET arguments:
prb_id - Probe ID msm_id - Measurement ID graph - graph name. Predefined collection of graphs currently 'tiny_rtt' and 'default'. If not defined - 'default' is assumed type - type of the graphs: 'minutely' : 'end-7200' - 'now' 'hourly' : 'end-28800' - 'now' 'daily' : 'end-90000' - 'now' 'weekly' : 'end-691200' - 'now' 'monthly' : 'end-2678400' - 'now' 'yearly' : 'end-31536000' - 'now'
start - when graph should begin (see AT-STYLE TIME SPECIFICATION on RRD fetch page) end - when graph should end, same as start but also included keyword 'last', that end the graph at the last entered measurement 'start' and 'end' override 'type' width - width of the graph canvas in pixels (Title, legend, axis names are not included) height - canvas height in pixels (Title, legend, axis names are not included)
Best regards,
/vty
participants (3)
-
Robert Kisteleki -
Viktor Naoumov -
Wilfried Woeber, UniVie/ACOnet