There are two things that you can do to help us to understand more about the performance issues you experience:
- On occasions when you experience issues with NU Service (of any sort) it is useful to know which web server was serving your NU Service session. To find this information delete the end of the URL to leave only https://nuservice.ncl.ac.uk/ within your address bar and type secure after the forward slash. For example:
If an analysts screen froze while they were reading a ticket with the URL: https://nuservice.ncl.ac.uk/LDSD.WebAccess.Integrated/wd/object/open.rails?class_name=ProblemManagement.Problem&key=82377f3f-6007-489d-b3f8-3d30ba4a6210. The URL should be edited to become: https://nuservice.ncl.ac.uk/secure
You will then be presented with a page of code, much of which can be ignored; the only part we are interested in is the first line of text at the top of the page (formatted in BOLD). Examples include: itsmweb3.ncl.ac.uk or itsmweb4.ncl.ac.uk. It is this text that indicates the web server in use at the time of the issues.
Please provide this piece of information together with the date/time of the issues and a description of the issue to the Service Desk.
- If you perceive NU Service to be running slow for you, you can use F12 developer tools in Chrome to gather the actual times taken for page loads.
To find this information, see our ‘how to guide’: F12 Developer tools.
If you are concerned about load times then please provide details of the times together with the actions you were carrying out on the system and the date/time.
Thank you for any feedback.