Skip to content
Snippets Groups Projects
Select Git revision
  • move-gl-dropdown
  • improve-table-pagination-spec
  • move-markdown-preview
  • winh-fix-merge-request-spec
  • master default
  • index-namespaces-lower-name
  • winh-single-karma-test
  • 10-3-stable
  • 36782-replace-team-user-role-with-add_role-user-in-specs
  • winh-modal-internal-state
  • tz-ide-file-icons
  • 38869-milestone-select
  • update-autodevops-template
  • jivl-activate-repo-cookie-preferences
  • qa-add-deploy-key
  • docs-move-article-ldap
  • 40780-choose-file
  • 22643-manual-job-page
  • refactor-cluster-show-page-conservative
  • dm-sidekiq-versioning
  • v10.4.0.pre
  • v10.3.0
  • v10.3.0-rc5
  • v10.3.0-rc4
  • v10.3.0-rc3
  • v10.3.0-rc2
  • v10.2.5
  • v10.3.0-rc1
  • v10.0.7
  • v10.1.5
  • v10.2.4
  • v10.2.3
  • v10.2.2
  • v10.2.1
  • v10.3.0.pre
  • v10.2.0
  • v10.2.0-rc4
  • v10.2.0-rc3
  • v10.1.4
  • v10.2.0-rc2
40 results

request_profiling.md

Forked from GitLab.org / GitLab FOSS
4430 commits behind the upstream repository.

Request Profiling

Procedure

  1. Grab the profiling token from Monitoring > Requests Profiles admin page (highlighted in a blue in the image below). Profile token
  2. Pass the header X-Profile-Token: <token> to the request you want to profile. You can use any of these tools
    • ModHeader Chrome extension
    • Modify Headers Firefox extension
    • curl --header 'X-Profile-Token: <token>' https://gitlab.example.com/group/project
  3. Once request is finished (which will take a little longer than usual), you can view the profiling output from Monitoring > Requests Profiles admin page. Profiling output

Cleaning up

Profiling output will be cleared out every day via a Sidekiq worker.