diff options
Diffstat (limited to 'doc/operations')
| -rw-r--r-- | doc/operations/incident_management/manage_incidents.md | 15 | ||||
| -rw-r--r-- | doc/operations/incident_management/status_page.md | 2 | ||||
| -rw-r--r-- | doc/operations/index.md | 9 | ||||
| -rw-r--r-- | doc/operations/tracing.md | 10 |
4 files changed, 7 insertions, 29 deletions
diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md index 28c4adec250..ba21a210359 100644 --- a/doc/operations/incident_management/manage_incidents.md +++ b/doc/operations/incident_management/manage_incidents.md @@ -201,31 +201,18 @@ In GitLab 15.1 and earlier, the escalation policy for [incidents created from al reflects the alert's escalation policy and cannot be changed. In [GitLab 15.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/356057), the incident escalation policy is independent and can be changed. -<!--- start_remove The following content will be removed on remove_date: '2023-08-22' --> - -## Embed metrics (removed) - -This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7 -and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0. - -<!--- end_remove --> - ## Close an incident Prerequisites: - You must have at least the Reporter role for the project. -To close an incident, in the upper-right corner, select **Close incident**. +To close an incident, in the upper-right corner, select **Incident actions** (**{ellipsis_v}**) and then **Close incident**. When you close an incident that is linked to an [alert](alerts.md), the linked alert's status changes to **Resolved**. You are then credited with the alert's status change. -<!-- Delete when the `move_close_into_dropdown` feature flag is removed --> -If you don't see this action at the top of an incident, your project or instance might have -enabled a feature flag to [moved it in the actions menu](../../user/project/issues/managing_issues.md#move-the-close-button-into-the-actions-menu). - ### Automatically close incidents via recovery alerts > [Introduced for HTTP integrations](https://gitlab.com/gitlab-org/gitlab/-/issues/13402) in GitLab 13.4. diff --git a/doc/operations/incident_management/status_page.md b/doc/operations/incident_management/status_page.md index 682b2ffd705..1d376301250 100644 --- a/doc/operations/incident_management/status_page.md +++ b/doc/operations/incident_management/status_page.md @@ -159,7 +159,7 @@ To publish comments to the Status Page Incident: - Create a comment on the incident issue. - When you're ready to publish the comment, mark the comment for publication by - adding a microphone [emoji reaction](../../user/award_emojis.md) + adding a microphone [emoji reaction](../../user/emoji_reactions.md) reaction (`:microphone:` 🎤) to the comment. - Any files attached to the comment (up to 5000 per issue) are also published. ([Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/205166) in GitLab 13.1.) diff --git a/doc/operations/index.md b/doc/operations/index.md index 73925afb2d8..766047e1f29 100644 --- a/doc/operations/index.md +++ b/doc/operations/index.md @@ -9,15 +9,6 @@ info: To determine the technical writer assigned to the Stage/Group associated w GitLab provides a variety of tools to help operate and maintain your applications. -<!--- start_remove The following content will be removed on remove_date: '2023-08-22' --> - -## Measure reliability and stability with metrics (removed) - -This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7 -and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0. - -<!--- end_remove --> - ## Manage alerts and incidents GitLab helps reduce alert fatigue for IT responders by providing tools to identify diff --git a/doc/operations/tracing.md b/doc/operations/tracing.md index 608a9c998f8..1df644f4de4 100644 --- a/doc/operations/tracing.md +++ b/doc/operations/tracing.md @@ -6,11 +6,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w # Distributed tracing **(ULTIMATE SAAS EXPERIMENT)** -> Introduced in GitLab 16.3 [with flags](../administration/feature_flags.md) named `observability_group_tab` and `observability_tracing`. Disabled by default. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124966) in GitLab 16.2 [with flags](../administration/feature_flags.md) named `observability_group_tab` and `observability_tracing`. Disabled by default. This feature is an [Experiment](../policy/experiment-beta-support.md#experiment). +> - Feature flag `observability_group_tab` [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133264) in GitLab 16.5. FLAG: -On GitLab.com, by default this feature is not available. To make it available, -an administrator can [enable the feature flags](../administration/feature_flags.md) named `observability_group_tab` and `observability_tracing`. +On GitLab.com, by default this feature is not available. +To make it available, an administrator can [enable the feature flag](../administration/feature_flags.md) named `observability_tracing`. The feature is not ready for production use. With distributed tracing, you can troubleshoot application performance issues by inspecting how a request moves through different services and systems, the timing of each operation, and any errors or logs as they occur. Tracing is particularly useful in the context of microservice applications, which group multiple independent services collaborating to fulfill user requests. @@ -32,11 +33,10 @@ Prerequisites: To enable tracing in a project: -1. On the left sidebar, select **Search or go to** and find your group. +1. On the left sidebar, select **Search or go to** and find your project. 1. Select **Settings > Access Tokens**. 1. Create an access token with the following scopes: `read_api`, `read_observability`, `write_observability`. 1. Copy the value of the access token. -1. Navigate to your project. 1. Select **Monitor > Tracing**. 1. Select **Enable**. |