Merge branch 'docs-monitor-nav-changes' into 'master'

Change Operations to Monitor in Monitor docs

See merge request gitlab-org/gitlab!63691

doc/operations/error_tracking.md

@@ -27,16 +27,16 @@ least Maintainer [permissions](../user/permissions.md) to enable the Sentry inte
 1. [Create](https://docs.sentry.io/product/sentry-basics/guides/integrate-frontend/create-new-project/) a new Sentry project. For each GitLab project that you want to integrate, we recommend that you create a new Sentry project.
 1. [Find or generate](https://docs.sentry.io/api/auth/) a Sentry auth token for your Sentry project.
    Make sure to give the token at least the following scopes: `event:read` and `project:read`.
-1. In GitLab, navigate to your project's **Operations > Error Tracking** page, and
+1. In GitLab, navigate to your project's **Monitor > Error Tracking** page, and
    click **Enable Error Tracking**.
-1. Navigate to your project's **Settings > Operations**. In the **Error Tracking** section,
+1. Navigate to your project's **Settings > Monitor**. In the **Error Tracking** section,
    ensure the **Active** checkbox is set.
 1. In the **Sentry API URL** field, enter your Sentry hostname. For example, enter `https://sentry.example.com` if this is the address at which your Sentry instance is available. For the SaaS version of Sentry, the hostname is `https://sentry.io`.
 1. In the **Auth Token** field, enter the token you previously generated.
 1. Click the **Connect** button to test the connection to Sentry and populate the **Project** dropdown.
 1. From the **Project** dropdown, choose a Sentry project to link to your GitLab project.
 1. Click **Save changes** for the changes to take effect.
-1. You can now visit **Operations > Error Tracking** in your project's sidebar to [view a list](#error-tracking-list) of Sentry errors.
+1. You can now visit **Monitor > Error Tracking** in your project's sidebar to [view a list](#error-tracking-list) of Sentry errors.
 
 ### Enabling GitLab issues links
 
@@ -45,7 +45,7 @@ You may also want to enable Sentry's GitLab integration by following the steps i
 ## Error Tracking List
 
 Users with at least Reporter [permissions](../user/permissions.md)
-can find the Error Tracking list at **Operations > Error Tracking** in your project's sidebar.
+can find the Error Tracking list at **Monitor > Error Tracking** in your project's sidebar.
 Here, you can filter errors by title or by status (one of Ignored , Resolved, or Unresolved) and sort in descending order by Frequency, First Seen, or Last Seen. By default, the error list is ordered by Last Seen and filtered to Unresolved errors.
 
 ![Error Tracking list](img/error_tracking_list_v12_6.png)

doc/operations/incident_management/alerts.md

@@ -11,7 +11,7 @@ Alerts are a critical entity in your incident management workflow. They represen
 ## Alert List
 
 Users with at least Developer [permissions](../../user/permissions.md) can
-access the Alert list at **Operations > Alerts** in your project's
+access the Alert list at **Monitor > Alerts** in your project's
 sidebar. The Alert list displays alerts sorted by start time, but
 you can change the sort order by clicking the headers in the Alert list.
 ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/217745) in GitLab 13.1.)
@@ -95,7 +95,7 @@ instance.
 To view the metrics for an alert:
 
 1. Sign in as a user with Developer or higher [permissions](../../user/permissions.md).
-1. Navigate to **Operations > Alerts**.
+1. Navigate to **Monitor > Alerts**.
 1. Select the alert you want to view.
 1. Below the title of the alert, select the **Metrics** tab.
 
@@ -115,7 +115,7 @@ your application's performance and how to resolve any problems.
 To view the logs for an alert:
 
 1. Sign in as a user with Developer or higher [permissions](../../user/permissions.md).
-1. Navigate to **Operations > Alerts**.
+1. Navigate to **Monitor > Alerts**.
 1. Select the alert you want to view.
 1. Below the title of the alert, select the **Metrics** tab.
 1. Select the [menu](../metrics/dashboards/index.md#chart-context-menu) of
@@ -168,7 +168,7 @@ difficult to track who is investigating and working on it. Assigning alerts ease
 
 To assign an alert:
 
-1. To display the list of current alerts, navigate to **Operations > Alerts**.
+1. To display the list of current alerts, navigate to **Monitor > Alerts**.
 
 1. Select your desired alert to display its details.
 
@@ -193,7 +193,7 @@ You can manually create [To-Do list items](../../user/todos.md) for yourself
 from the Alert details screen, and view them later on your **To-Do List**. To
 add a to-do item:
 
-1. To display the list of current alerts, navigate to **Operations > Alerts**.
+1. To display the list of current alerts, navigate to **Monitor > Alerts**.
 1. Select your desired alert to display its **Alert Management Details View**.
 1. Select the **Add a to do** button in the right sidebar:
 

doc/operations/incident_management/incidents.md

@@ -26,7 +26,7 @@ Incident, you have two options to do this manually.
 
 > [Moved](https://gitlab.com/gitlab-org/monitor/health/-/issues/24) to GitLab Free in 13.3.
 
-- Navigate to **Operations > Incidents** and click **Create Incident**.
+- Navigate to **Monitor > Incidents** and click **Create Incident**.
 - Create a new issue using the `incident` template available when creating it.
 - Create a new issue and assign the `incident` label to it.
 
@@ -51,7 +51,7 @@ Incident, you have two options to do this manually.
 With Maintainer or higher [permissions](../../user/permissions.md), you can enable
  GitLab to create incident automatically whenever an alert is triggered:
 
-1. Navigate to **Settings > Operations > Incidents** and expand **Incidents**.
+1. Navigate to **Settings > Monitor > Incidents** and expand **Incidents**.
 1. Check the **Create an incident** checkbox.
 1. To customize the incident, select an
    [issue template](../../user/project/description_templates.md#create-an-issue-template).
@@ -70,7 +70,7 @@ for each PagerDuty incident. This configuration requires you to make changes
 in both PagerDuty and GitLab:
 
 1. Sign in as a user with the [Maintainer role](../../user/permissions.md).
-1. Navigate to **Settings > Operations > Incidents** and expand **Incidents**.
+1. Navigate to **Settings > Monitor > Incidents** and expand **Incidents**.
 1. Select the **PagerDuty integration** tab:
 
    ![PagerDuty incidents integration](img/pagerduty_incidents_integration_v13_3.png)
@@ -87,7 +87,7 @@ confirm that a GitLab incident is created from the incident.
 ## Incident list
 
 For users with at least Guest [permissions](../../user/permissions.md), the
-Incident list is available at **Operations > Incidents**
+Incident list is available at **Monitor > Incidents**
 in your project's sidebar. The list contains the following metrics:
 
 ![Incident List](img/incident_list_v13_5.png)
@@ -132,7 +132,7 @@ For a live example of the incident list in action, visit this
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230847) in GitLab 13.4.
 
 Users with at least Guest [permissions](../../user/permissions.md) can view
-the Incident Details page. Navigate to **Operations > Incidents** in your project's
+the Incident Details page. Navigate to **Monitor > Incidents** in your project's
 sidebar, and select an incident from the list.
 
 When you take any of these actions on an incident, GitLab logs a system note and
@@ -208,7 +208,7 @@ remaining before the SLA period expires. The timer is also dynamically updated
 every 15 minutes so you do not have to refresh the page to see the time remaining.
 To configure the timer:
 
-1. Navigate to **Settings > Operations**.
+1. Navigate to **Settings > Monitor**.
 1. Scroll to **Incidents** and click **Expand**, then select the
    **Incident settings** tab.
 1. Select **Activate "time to SLA" countdown timer**.
@@ -278,7 +278,7 @@ templates.
 With Maintainer or higher [permissions](../../user/permissions.md), you can enable
  GitLab to close an incident automatically when a **Recovery Alert** is received:
 
-1. Navigate to **Settings > Operations > Incidents** and expand **Incidents**.
+1. Navigate to **Settings > Monitor > Incidents** and expand **Incidents**.
 1. Check the **Automatically close associated Incident** checkbox.
 1. Click **Save changes**.
 

doc/operations/incident_management/integrations.md

@@ -19,7 +19,7 @@ to use this endpoint.
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/245331) in GitLab Free 13.5.
 
 With the [Maintainer role or higher](../../user/permissions.md),
-you can view the list of configured alerts integrations by navigating to **Settings > Operations**
+you can view the list of configured alerts integrations by navigating to **Settings > Monitor**
 in your project's sidebar menu, and expanding the **Alerts** section. The list displays
 the integration name, type, and status (enabled or disabled):
 
@@ -38,7 +38,7 @@ receive alert payloads in JSON format. You can always
 
 1. Sign in to GitLab as a user with maintainer [permissions](../../user/permissions.md)
    for a project.
-1. Navigate to **Settings > Operations** in your project.
+1. Navigate to **Settings > Monitor** in your project.
 1. Expand the **Alerts** section, and in the **Select integration type** dropdown menu,
    select **HTTP Endpoint**.
 1. Toggle the **Active** alert setting. The URL and Authorization Key for the webhook configuration
@@ -55,7 +55,7 @@ and you can [customize the payload](#customize-the-alert-payload-outside-of-gitl
 
 1. Sign in to GitLab as a user with maintainer [permissions](../../user/permissions.md)
    for a project.
-1. Navigate to **Settings > Operations** in your project.
+1. Navigate to **Settings > Monitor** in your project.
 1. Expand the **Alerts** section.
 1. For each endpoint you want to create:
 
@@ -166,7 +166,7 @@ configures an integration, you can trigger a test
 alert to confirm your integration works properly.
 
 1. Sign in as a user with Developer or greater [permissions](../../user/permissions.md).
-1. Navigate to **Settings > Operations** in your project.
+1. Navigate to **Settings > Monitor** in your project.
 1. Click **Alerts** to expand the section.
 1. Click the **{settings}** settings icon on the right side of the integration in [the list](#integrations-list).
 1. Select the **Send test alert** tab to open it.
@@ -220,7 +220,7 @@ active at the same time.
 To enable Opsgenie integration:
 
 1. Sign in as a user with the [Maintainer or Owner role](../../user/permissions.md).
-1. Navigate to **Operations > Alerts**.
+1. Navigate to **Monitor > Alerts**.
 1. In the **Integrations** select box, select **Opsgenie**.
 1. Select the **Active** toggle.
 1. In the **API URL** field, enter the base URL for your Opsgenie integration,
@@ -228,4 +228,4 @@ To enable Opsgenie integration:
 1. Select **Save changes**.
 
 After you enable the integration, navigate to the Alerts list page at
-**Operations > Alerts**, and then select **View alerts in Opsgenie**.
+**Monitor > Alerts**, and then select **View alerts in Opsgenie**.

doc/operations/incident_management/oncall_schedules.md

@@ -28,7 +28,7 @@ Set up an on-call schedule for your team to add rotations to.
 
 Follow these steps to create a schedule:
 
-1. Go to **Operations > On-call Schedules** and select **Add a schedule**.
+1. Go to **Monitor > On-call Schedules** and select **Add a schedule**.
 1. In the **Add schedule** form, enter the schedule's name and description, and select a timezone.
 1. Click **Add schedule**.
 
@@ -41,7 +41,7 @@ create [rotations](#rotations) for your schedule.
 
 Follow these steps to update a schedule:
 
-1. Go to **Operations > On-call Schedules** and select the **Pencil** icon on the top right of the
+1. Go to **Monitor > On-call Schedules** and select the **Pencil** icon on the top right of the
    schedule card, across from the schedule name.
 1. In the **Edit schedule** form, edit the information you wish to update.
 1. Click the **Edit schedule** button to save your changes.
@@ -53,7 +53,7 @@ interval (if one is set) to the corresponding times in the new time zone.
 
 Follow these steps to delete a schedule:
 
-1. Go to **Operations > On-call Schedules** and select the **Trash Can** icon on the top right of the
+1. Go to **Monitor > On-call Schedules** and select the **Trash Can** icon on the top right of the
    schedule card.
 1. In the **Delete schedule** window, click the **Delete schedule** button.
 
@@ -63,7 +63,7 @@ Add rotations to an existing schedule to put your team members on-call.
 
 Follow these steps to create a rotation:
 
-1. Go to **Operations > On-call Schedules** and select **Add a rotation** on the top right of the
+1. Go to **Monitor > On-call Schedules** and select **Add a rotation** on the top right of the
    current schedule.
 1. In the **Add rotation** form, enter the following:
 
@@ -80,7 +80,7 @@ Follow these steps to create a rotation:
 
 Follow these steps to edit a rotation:
 
-1. Go to **Operations > On-call Schedules** and select the **Pencil** icon to the right of the title
+1. Go to **Monitor > On-call Schedules** and select the **Pencil** icon to the right of the title
    of the rotation that you want to update.
 1. In the **Edit rotation** form, make the changes that you want.
 1. Select the **Edit rotation** button.
@@ -89,7 +89,7 @@ Follow these steps to edit a rotation:
 
 Follow these steps to delete a rotation:
 
-1. Go to **Operations > On-call Schedules** and select the **Trash Can** icon to the right of the
+1. Go to **Monitor > On-call Schedules** and select the **Trash Can** icon to the right of the
    title of the rotation that you want to delete.
 1. In the **Delete rotation** window, select the **Delete rotation** button.
 

doc/operations/incident_management/paging.md

@@ -27,7 +27,7 @@ Email notifications are available in projects for triggered alerts. Project
 members with the **Owner** or **Maintainer** roles have the option to receive
 a single email notification for new alerts.
 
-1. Navigate to **Settings > Operations**.
+1. Navigate to **Settings > Monitor**.
 1. Expand the **Alerts** section.
 1. In the **Integration settings** tab, select the checkbox
    **Send a single email notification to Owners and Maintainers for new alerts**.

doc/operations/incident_management/status_page.md

@@ -42,7 +42,7 @@ Only AWS S3 is supported as a deploy target.
 To provide GitLab with the AWS account information needed to push content to your Status Page:
 
 1. Sign into GitLab as a user with Maintainer or greater [permissions](../../user/permissions.md).
-1. Navigate to **{settings}** **Settings > Operations**. Next to **Status Page**,
+1. Navigate to **{settings}** **Settings > Monitor**. Next to **Status Page**,
    click **Expand**.
 1. Click **Active** to enable the Status Page feature.
 1. In **Status Page URL**, provide the URL to your external status page.
@@ -92,10 +92,9 @@ the issue can potentially [publish comments to your GitLab Status Page](#publish
 After creating the CI/CD variables, configure the Project you want to use for
 Incident issues:
 
-1. To view the [Operations Settings](../../user/project/settings/#operations-settings)
-   page, navigate to **{settings}** **Settings > Operations > Status Page**.
-1. Fill in your cloud provider's credentials and make sure the **Active** checkbox is checked.
-1. Click **Save changes**.
+1. To view the Status Page settings, navigate to **{settings}** **Settings > Monitor > Status Page**.
+1. Fill in your cloud provider's credentials and make sure to select the **Active** checkbox.
+1. Select **Save changes**.
 
 ## How to use your GitLab Status Page
 

doc/operations/metrics/alerts.md

@@ -25,7 +25,7 @@ For managed Prometheus instances using auto configuration, you can
 [configure alerts for metrics](index.md#adding-custom-metrics) directly in the
 [metrics dashboard](index.md). To set an alert:
 
-1. In your project, navigate to **Operations > Metrics**,
+1. In your project, navigate to **Monitor > Metrics**,
 1. Identify the metric you want to create the alert for, and click the
    **ellipsis** **{ellipsis_v}** icon in the top right corner of the metric.
 1. Choose **Alerts**.
@@ -110,7 +110,7 @@ Prometheus server to use the
 Alerts can be used to trigger actions, like opening an issue automatically
 (disabled by default since `13.1`). To configure the actions:
 
-1. Navigate to your project's **Settings > Operations > Alerts**.
+1. Navigate to your project's **Settings > Monitor > Alerts**.
 1. Enable the option to create issues.
 1. Choose the [issue template](../../user/project/description_templates.md) to create the issue from.
 1. Optionally, select whether to send an email notification to the developers of the project.

doc/operations/metrics/dashboards/index.md

@@ -20,14 +20,14 @@ or [duplicate a GitLab-defined Prometheus dashboard](#duplicate-a-gitlab-defined
 
 You can configure a custom dashboard by adding a new YAML file into your project's
 `.gitlab/dashboards/` directory. For the dashboard to display on your project's
-**Operations > Metrics** page, the files must have a `.yml`
+**Monitor > Metrics** page, the files must have a `.yml`
 extension and be present in your project's **default** branch.
 
 To create a new dashboard from the GitLab user interface:
 
 1. Sign in to GitLab as a user with Maintainer or Owner
    [permissions](../../../user/permissions.md#project-members-permissions).
-1. Navigate to your dashboard at **Operations > Metrics**.
+1. Navigate to your dashboard at **Monitor > Metrics**.
 1. In the top-right corner of your dashboard, click the **{ellipsis_v}** **More actions** menu,
    and select **Create new**:
    ![Monitoring Dashboard actions menu with create new item](img/actions_menu_create_new_dashboard_v13_3.png)
@@ -60,7 +60,7 @@ To create a new dashboard from the command line:
    ```
 
 1. Save the file, commit, and push to your repository. The file must be present in your **default** branch.
-1. Navigate to your project's **Operations > Metrics** and choose the custom
+1. Navigate to your project's **Monitor > Metrics** and choose the custom
    dashboard from the dropdown.
 
 Your custom dashboard is available at `https://example.com/project/-/metrics/custom_dashboard_name.yml`.

doc/operations/metrics/dashboards/settings.md

@@ -21,7 +21,7 @@ time zone, but you can display dates and times in UTC format. To change the
 time zone:
 
 1. Sign in as a user with Manage Project Operations [permissions](../../../user/permissions.md).
-1. Navigate to **Settings > Operations**.
+1. Navigate to **Settings > Monitor**.
 1. Scroll to **Metrics Dashboard** and click **Expand**.
 1. In the **Dashboard timezone** select box, select *User's local timezone*
    or *UTC*:
@@ -37,7 +37,7 @@ You can add a button on your monitoring dashboard that links directly to your
 existing external dashboards:
 
 1. Sign in as a user with Manage Project Operations [permissions](../../../user/permissions.md).
-1. Navigate to **Settings > Operations**.
+1. Navigate to **Settings > Monitor**.
 1. Scroll to **Metrics Dashboard** and click **Expand**.
 1. In **External dashboard URL**, provide the URL to your external dashboard:
 

doc/operations/metrics/embed_grafana.md

@@ -47,7 +47,7 @@ format. To embed panels from a Grafana instance, the data source must be:
 To set up the Grafana API in Grafana:
 
 1. In Grafana, [generate an Admin-level API Token](https://grafana.com/docs/grafana/latest/http_api/auth/#create-api-token).
-1. In your GitLab project, go to **Settings > Operations** and expand the **Grafana authentication**
+1. In your GitLab project, go to **Settings > Monitor** and expand the **Grafana authentication**
    section.
 1. To enable the integration, check the **Active** checkbox.
 1. For **Grafana URL**, enter the base URL of the Grafana instance.

doc/operations/metrics/index.md

@@ -36,7 +36,7 @@ your Prometheus integration depends on where your apps are running:
   and define at least one environment.
 - **For a cluster integrated Prometheus** - GitLab can query
   [an in-cluster Prometheus](../../user/clusters/integrations.md#prometheus-cluster-integration).
-  You must also complete a code deployment to your cluster for the **Operations > Metrics**
+  You must also complete a code deployment to your cluster for the **Monitor > Metrics**
   page to contain data. You can do this using [Auto DevOps](../../topics/autodevops/quick_start_guide.md).
 
 ![Monitoring Dashboard](img/prometheus_monitoring_dashboard_v13_3.png)
@@ -57,7 +57,7 @@ To view the [default metrics dashboard](dashboards/default.md) for an environmen
 
 1. *If the metrics dashboard is only visible to project members,* sign in to
    GitLab as a member of a project. Learn more about [metrics dashboard visibility](#metrics-dashboard-visibility).
-1. In your project, navigate to **Operations > Metrics**.
+1. In your project, navigate to **Monitor > Metrics**.
 
 GitLab displays the [default metrics dashboard](dashboards/default.md) for the environment,
 like the following example:

doc/operations/tracing.md

@@ -34,7 +34,7 @@ GitLab provides an easy way to open the Jaeger UI from within your project:
 
 1. [Set up Jaeger](https://www.jaegertracing.io) and configure your application using one of the
    [client libraries](https://www.jaegertracing.io/docs/latest/client-libraries/).
-1. Navigate to your project's **Settings > Operations** and provide the Jaeger URL.
+1. Navigate to your project's **Settings > Monitor** and provide the Jaeger URL.
 1. Click **Save changes** for the changes to take effect.
-1. You can now visit **Operations > Tracing** in your project's sidebar and GitLab redirects you to
+1. You can now visit **Monitor > Tracing** in your project's sidebar and GitLab redirects you to
    the configured Jaeger URL.

doc/user/project/clusters/index.md

@@ -31,7 +31,7 @@ Besides integration at the project level, Kubernetes clusters can also be
 integrated at the [group level](../../group/clusters/index.md) or
 [GitLab instance level](../../instance/clusters/index.md).
 
-To view your project level Kubernetes clusters, navigate to **Operations > Kubernetes**
+To view your project level Kubernetes clusters, navigate to **Infrastructure > Kubernetes**
 from your project. On this page, you can [add a new cluster](#adding-and-removing-clusters)
 and view information about your existing clusters, such as:
 
@@ -187,7 +187,7 @@ your cluster. This can cause deployment jobs to fail.
 
 To clear the cache:
 
-1. Navigate to your project's **Operations > Kubernetes** page, and select your cluster.
+1. Navigate to your project's **Infrastructure > Kubernetes** page, and select your cluster.
 1. Expand the **Advanced settings** section.
 1. Click **Clear cluster cache**.
 

doc/user/project/clusters/kubernetes_pod_logs.md

@@ -44,12 +44,11 @@ a [metrics dashboard](../../../operations/metrics/index.md) and select **View lo
 
 1. Sign in as a user with the _View pod logs_
    [permissions](../../permissions.md#project-members-permissions) in the project.
-1. *To navigate to the **Log Explorer** from the sidebar menu,* go to
-   **{cloud-gear}** **Operations > Pod logs**.
-   ([Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22011) in GitLab 12.5.)
-1. *To navigate to the **Log Explorer** from a specific pod on a [Deploy Board](../deploy_boards.md):*
+1. To navigate to the **Log Explorer** from the sidebar menu, go to **Monitor > Logs**
+   ([Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22011) in GitLab 12.5.).
+1. To navigate to the **Log Explorer** from a specific pod on a [Deploy Board](../deploy_boards.md):
 
-   1. Go to **{cloud-gear}** **Operations > Environments** and find the environment
+   1. Go to **Deployments > Environments** and find the environment
       which contains the desired pod, like `production`.
    1. On the **Environments** page, you should see the status of the environment's
       pods with [Deploy Boards](../deploy_boards.md).

doc/user/project/settings/index.md

@@ -415,7 +415,7 @@ NOTE:
 Only project Owners have the [permissions](../../permissions.md#project-members-permissions)
 to remove a fork relationship.
 
-## Operations settings
+## Monitor settings
 
 ### Alerts