Overview
There is key information available in the Response header of sharefile pages in Sharepoint, and you can make use of Catchpoint's Insights feature to capture those headers and monitor Sharepoint's performance.
What are those metrics and what do they tell us?
The following metrics found in Sharepoint's headers can help you identify server-specific performance issues.
- SPRequestDuration (ms): The amount of time the server spent processing the page request
- (SP)IISLatency (ms): The amount of time the page request waited on the server before getting processed
- X-SharePointHealthScore: This is the value, from zero to ten, that indicates how heavily loaded the SharePoint Server was at the time when the page was served. A score of zero means the server is not under load, while a score of ten means the server is overloaded. Ideally, this value should be zero or close to it.
How to capture these values
- Test Setup: You can use a web transaction test to script the flow, or you can use the existing catchpoint SAAS templates available in the portal.
- Insights: Once you have the test ready, youe can use the Insights (indicators) to capture these metrics. Please find the below insight details.
| Insight name | Regex |
|---|---|
| SP-iis-latency | spiislatency:\s(\d\*\\.\*\d\*) |
| SP request duration | sprequestduration:\s(\d\*\\.\*\d\*) |
| Sharepoint health score | x-sharepointhealthscore:\s(\d\*\\.\*\d\*) |
In our internal testing we captured the server performance issue below. In the graph we can see there is a spike in Response and Wait time which can be correlated with the spike in SP request duration. This shows the spoke was not due to a network issue, but the amount of time the server took to process the request was high.
