Advice on Grafana JIRA Request Duration Dashboard (High Average "/sr" Wait Times showing)

Hi Everyone,

I am a newby to Grafana (learning on the fly after inheriting the monitoring role in my Team and having my Manager ask me to look into one of the Grafana charts).

Essentially the chart is a Grafana JIRA Request Duration dashboard/chart and has a bunch of metrics and graphs for various JIRA parameters.

I’m not sure if the dashboard/chart is an off-the-shelf one included with Grafana or if one of my predecessors has created it.

The chart shows what appear to be various parameters that are being monitored for “average wait time” and these include:

/sr
/browse
/issues
/activity
/projects
/plugins


/download
/charts
/osd.jsp
/images
/jira

I’m not sure what the “/sr” option is, but since 16th August the graph for the average wait time has increased from an indistinguishable 200ms up to now averaging between about 2 sec and 5 sec (and it fluctuates like the sine wave it is and is the highest “average wait” event in the chart).

Would anyone be able to advise what the “/sr” event is or advise where I could find additional information about it (I’ve searched Google for “Grafana Request Duration Jira /sr” but it hasn’t really helped).

If I can work out how to paste a screen shot of the chart in here, I’ll gladly add it to this post in hope it helps !

Any help would be greatly appreciated.

Kind Regards.
Damion

what is the rest api endpoint or data source for all of these endpoints?

might be good to check this out

OK, issue has been resolved.

I found entries in the JIRA access logs for the past 5 days showing the GET “/sr” API call recurring every 30 seconds (with a username and TCPIP number included in every line).

Was able to track the developer down and essentially the cause was that they had written a test harness to hit the JIRA API “/sr” endpoint every 30 seconds to retrieve some filtered data from a project in JIRA.

This manifested itself in the Grafana “Request Duration” chart as high wait times for the “/sr” endpoint.

The developer has agreed to change the test harness so it runs on a “manual” basis rather than automatically every 30 seconds.

1 Like