perfSONAR User Q&A and Other Discussion

[Michael Johnson <>]

Hi Hyojoon,

Thanks for your bug report. We're looking into it. Looking at your MA, it 
looks like you're getting 500 errors for some requests, i.e.:

http://perfsonar-ma-2.princeton.edu/esmond/perfsonar/archive/dfbfe496326a49d1a55219ac831f9b26/histogram-owdelay/statistics/0?format=json

Do you see any interesting errors in /var/log/cassandra/cassandra.log or /var/log/cassandra/system.log? These could be preventing the graphs from getting all the necessary data. 

I suspect there are some issues with your MA's summary windows, although it's 
not quite clear yet where the problem lies. I've opened a bug report here:
https://github.com/perfsonar/graphs/issues/33

I put it with the graphs, even though it's not clear yet whether it's a 
problem with the charts themselves, or esmond.

Thanks,
Michael

On Wed, Mar 09, 2016 at 08:25:22PM +0000, Hyojoon Kim wrote:
> Hi,
>
> After an upgrade to v3.5-1, the chart that shows measured data seems to have 
> a display issue. To be more specific, the chart does not display all 
> available ‘Latency’ data it has *when zoomed to 1 day* by mouse *click* on 
> ‘1d’ above the chart (not by window dragging, which is below the chart).
>
> For example, the following links show charts that display measurement data 
> between two nodes (128.112.228.24 and 128.112.228.23). The query was made on 
> March 9, 2016, at around *2:54 pm*.  However, when zoomed to *1 day*, the 
> display cuts off at around 7:33 am. When zoomed to *3 day*, the data is 
> displayed up to roughly 2:54pm.
>
> In other words, zooming to *1d* seems to cut off displayed latency data, even 
> though the data *is* actually there.  Note that ‘Ping’ data is not cut off.
>
> Zoom: 1 day (1d)
> https://perfsonar-ma-2.princeton.edu/perfsonar-graphs/graphWidget.cgi?url=https://perfsonar-ma-2.princeton.edu/esmond/perfsonar/archive&source=perfsonar-hpcrc-delay.princeton.edu&dest=perfsonar-87prospect-delay.princeton.edu#timeframe=1d
>
> Zoom: 3 day (3d)
> https://perfsonar-ma-2.princeton.edu/perfsonar-graphs/graphWidget.cgi?url=https://perfsonar-ma-2.princeton.edu/esmond/perfsonar/archive&source=perfsonar-hpcrc-delay.princeton.edu&dest=perfsonar-87prospect-delay.princeton.edu#timeframe=3d
>
>
> * Zoomed to between 6am - 2:54pm by dragging the window with mouse, so that 
> the difference between 1d and 3d is more obvious (i.e., 1d zoom is missing 
> latency data)
>
> Zoom: 1 day
> https://perfsonar-ma-2.princeton.edu/perfsonar-graphs/graphWidget.cgi?url=https://perfsonar-ma-2.princeton.edu/esmond/perfsonar/archive&source=perfsonar-hpcrc-delay.princeton.edu&dest=perfsonar-87prospect-delay.princeton.edu#timeframe=1d&zoom_start=1457520917158&zoom_end=1457553245000
>
> Zoom: 3 day
> https://perfsonar-ma-2.princeton.edu/perfsonar-graphs/graphWidget.cgi?url=https://perfsonar-ma-2.princeton.edu/esmond/perfsonar/archive&source=perfsonar-hpcrc-delay.princeton.edu&dest=perfsonar-87prospect-delay.princeton.edu#timeframe=3d&zoom_start=1457520917158&zoom_end=1457553245000
>
>
> Any help or insight would help!
>
>
> Thanks,
> Joon

--
Michael Johnson
GlobalNOC Software Engineering
Indiana University

812-856-2771

Attachment: pgprOrpnJU86u.pgp
Description: PGP signature