PageRenderTime 19ms CodeModel.GetById 17ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/doc/administration/monitoring/performance/request_profiling.md

https://gitlab.com/visay/gitlab-ce
Markdown | 16 lines | 14 code | 2 blank | 0 comment | 0 complexity | bab43ce178dfee35cdc29626a52a1d0b MD5 | raw file
 1# Request Profiling
 2
 3## Procedure
 41. Grab the profiling token from `Monitoring > Requests Profiles` admin page
 5(highlighted in a blue in the image below).
 6![Profile token](img/request_profiling_token.png)
 71. Pass the header `X-Profile-Token: <token>` to the request you want to profile. You can use any of these tools
 8    * [ModHeader](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj) Chrome extension
 9    * [Modify Headers](https://addons.mozilla.org/en-US/firefox/addon/modify-headers/) Firefox extension
10    * `curl --header 'X-Profile-Token: <token>' https://gitlab.example.com/group/project`
111. Once request is finished (which will take a little longer than usual), you can
12view the profiling output from `Monitoring > Requests Profiles` admin page.
13![Profiling output](img/request_profile_result.png)
14
15## Cleaning up
16Profiling output will be cleared out every day via a Sidekiq worker.