Hi,
we noticed we have a lot of additional gadget requests facing our instance since the update. Is this a known behaviour with JIRA 7.2?
I only read about the gadgets calculation moved away from the server to the user browser via JS, but didn't read anything about http requests increasing by this change.
So I am looking for the cause of this.
image2016-10-17 13:16:14.png
regards
MPB
You've sort of answered your own question - as the gadgets are now doing the work on the client, they need to make more requests back to the server to get the raw data to work with. It's not just the gadgets either, there's other places where the system uses more REST calls back to itself.
I'm not sure I'd have expected it to go up 4 times, might be interesting to see what urls it is hitting.
Hey Nic Brough,
thank you for your answer.
That's what I thought to, why is 4 times higher now than before. Regarding the URLs, atleast 50% of the requests are hitting /rest/dashboard/1.0/ and other gadget related key words.
I don't know the URL structure, but is it possible to analyze it further and find out if there are certain gadgets who are causing this.
Some URL examples:
rest/dashboards/1.0/14100/gadget/17700/prefs?_=14775579564
/rest/dashboards/1.0/20021/gadget/28355/prefs?_=14775579559
/rest/dashboards/1.0/20806/gadget/30253/prefs?_=14775579564
/rest/gadgets/1.0/g/messagebundle/und/gadget.common%2Cgadge
/rest/gadgets/1.0/g/messagebundle/en_US/gadget.common%2Cgad
/rest/dashboards/1.0/10000/gadget/10002/prefs?_=14776444916
/rest/dashboards/1.0/20115/gadget/28777/prefs?_=14776444949
kind regards
Marc-Philip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not 100% sure of the structure either, but I think the first number (ignoring the 1.0) is the id of the dashboard in the databate, the second the gadget and the third the pointer to the settings. I'd analyse the impact of the gadget first - it may be that there's one particular gadget that's doing most of it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.