2020-06-04 03:08:05 +00:00
---
stage: Monitor
2020-10-19 21:09:06 +00:00
group: Health
2020-06-04 03:08:05 +00:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
2016-10-14 17:49:36 +00:00
# Request Profiling
2020-06-10 15:08:07 +00:00
To profile a request:
2018-11-29 23:07:14 +00:00
2020-06-10 15:08:07 +00:00
1. Sign in to GitLab as a user with Administrator or Maintainer [permissions ](../../../user/permissions.md ).
2020-07-29 00:09:37 +00:00
1. In the navigation bar, click **Admin area** .
2020-08-04 18:09:49 +00:00
1. Navigate to **Monitoring > Requests Profiles** .
2020-06-10 15:08:07 +00:00
1. In the **Requests Profiles** section, copy the token.
1. Pass the headers `X-Profile-Token: <token>` and `X-Profile-Mode: <mode>` (where
`<mode>` can be `execution` or `memory` ) to the request you want to profile. When
passing headers, you can use:
2016-10-14 17:49:36 +00:00
2020-06-10 15:08:07 +00:00
- Browser extensions such as the
[ModHeader ](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj )
Chrome extension.
- `curl` . For example:
2018-11-29 23:07:14 +00:00
2020-06-10 15:08:07 +00:00
```shell
curl --header 'X-Profile-Token: < token > ' --header 'X-Profile-Mode: < mode > ' "https://gitlab.example.com/group/project"
```
Profiled requests can take longer than usual.
After the request completes, you can view the profiling output from the
2020-08-04 18:09:49 +00:00
**Monitoring > Requests Profiles** administration page:
2020-06-10 15:08:07 +00:00
![Profiling output ](img/request_profile_result.png )
## Cleaning up profiled requests
The output from profiled requests is cleared out once each day through a
Sidekiq worker.