2020-06-23 00:09:42 +05:30
---
stage: Monitor
2021-01-03 14:25:43 +05:30
group: Health
2020-06-23 00:09:42 +05:30
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-11-03 12:29:30 +05:30
# Request Profiling
2020-06-23 00:09:42 +05:30
To profile a request:
1. Sign in to GitLab as a user with Administrator or Maintainer [permissions ](../../../user/permissions.md ).
2020-10-24 23:57:45 +05:30
1. In the navigation bar, click **Admin area** .
1. Navigate to **Monitoring > Requests Profiles** .
2020-06-23 00:09:42 +05:30
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:
- Browser extensions such as the
[ModHeader ](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj )
Chrome extension.
- `curl` . For example:
```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-10-24 23:57:45 +05:30
**Monitoring > Requests Profiles** administration page:
2019-02-15 15:39:39 +05:30
2020-06-23 00:09:42 +05:30
2016-11-03 12:29:30 +05:30
2020-06-23 00:09:42 +05:30
## Cleaning up profiled requests
2019-02-15 15:39:39 +05:30
2020-06-23 00:09:42 +05:30
The output from profiled requests is cleared out once each day through a
Sidekiq worker.
