Commit 4f7f273c authored by GitLab Bot's avatar GitLab Bot

Automatic merge of gitlab-org/gitlab-ce master

parents 96fa512b 386aeb71
---
title: Fix navigation style in docs
merge_request: 24090
author: Takuya Noguchi
type: other
...@@ -2,14 +2,14 @@ ...@@ -2,14 +2,14 @@
## Procedure ## Procedure
1. Grab the profiling token from `Monitoring > Requests Profiles` admin page 1. Grab the profiling token from **Monitoring > Requests Profiles** admin page
(highlighted in a blue in the image below). (highlighted in a blue in the image below).
![Profile token](img/request_profiling_token.png) ![Profile token](img/request_profiling_token.png)
1. Pass the header `X-Profile-Token: <token>` to the request you want to profile. You can use: 1. Pass the header `X-Profile-Token: <token>` to the request you want to profile. You can use:
- Browser extensions. For example, [ModHeader](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj) Chrome extension. - Browser extensions. For example, [ModHeader](https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj) Chrome extension.
- `curl`. For example, `curl --header 'X-Profile-Token: <token>' https://gitlab.example.com/group/project`. - `curl`. For example, `curl --header 'X-Profile-Token: <token>' https://gitlab.example.com/group/project`.
1. Once request is finished (which will take a little longer than usual), you can 1. Once request is finished (which will take a little longer than usual), you can
view the profiling output from `Monitoring > Requests Profiles` admin page. view the profiling output from **Monitoring > Requests Profiles** admin page.
![Profiling output](img/request_profile_result.png) ![Profiling output](img/request_profile_result.png)
## Cleaning up ## Cleaning up
......
...@@ -47,7 +47,7 @@ This project has three jobs: ...@@ -47,7 +47,7 @@ This project has three jobs:
## Store API keys ## Store API keys
You'll need to create two variables in `Settings > CI/CD > Variables` on your GitLab project settings: You'll need to create two variables in **Settings > CI/CD > Variables** in your GitLab project:
- `HEROKU_STAGING_API_KEY` - Heroku API key used to deploy staging app. - `HEROKU_STAGING_API_KEY` - Heroku API key used to deploy staging app.
- `HEROKU_PRODUCTION_API_KEY` - Heroku API key used to deploy production app. - `HEROKU_PRODUCTION_API_KEY` - Heroku API key used to deploy production app.
......
...@@ -30,7 +30,7 @@ GitLab can seamlessly deploy and manage Prometheus on a [connected Kubernetes cl ...@@ -30,7 +30,7 @@ GitLab can seamlessly deploy and manage Prometheus on a [connected Kubernetes cl
Once you have a connected Kubernetes cluster with Helm installed, deploying a managed Prometheus is as easy as a single click. Once you have a connected Kubernetes cluster with Helm installed, deploying a managed Prometheus is as easy as a single click.
1. Go to the `Operations > Kubernetes` page, to view your connected clusters 1. Go to the **Operations > Kubernetes** page to view your connected clusters
1. Select the cluster you would like to deploy Prometheus to 1. Select the cluster you would like to deploy Prometheus to
1. Click the **Install** button to deploy Prometheus to the cluster 1. Click the **Install** button to deploy Prometheus to the cluster
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment