Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
2f147005c5
commit
b6e23edd65
|
|
@ -1 +1 @@
|
|||
74fa51387fbc4ac199309f5c0461d4cdde2a1a2f
|
||||
1fae8b36711542e66b772164e159f29c14bb4ce4
|
||||
|
|
|
|||
|
|
@ -47,6 +47,11 @@ module Types
|
|||
null: false,
|
||||
description: 'Fields related to design management'
|
||||
|
||||
field :user, Types::UserType,
|
||||
null: true,
|
||||
description: 'Find a user',
|
||||
resolver: Resolvers::UserResolver
|
||||
|
||||
field :users, Types::UserType.connection_type,
|
||||
null: true,
|
||||
description: 'Find users',
|
||||
|
|
@ -56,11 +61,6 @@ module Types
|
|||
description: 'Text to echo back',
|
||||
resolver: Resolvers::EchoResolver
|
||||
|
||||
field :user, Types::UserType,
|
||||
null: true,
|
||||
description: 'Find a user',
|
||||
resolver: Resolvers::UserResolver
|
||||
|
||||
def design_management
|
||||
DesignManagementObject.new(nil)
|
||||
end
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ of the project shows some basic resource usage charts, such as CPU and memory us
|
|||
of each server in [Omnibus GitLab](https://docs.gitlab.com/omnibus/) installations.
|
||||
|
||||
You can also use the project to configure your own
|
||||
[custom metrics](../../../user/project/integrations/prometheus.md#adding-custom-metrics) using
|
||||
[custom metrics](../../../operations/metrics/index.md#adding-custom-metrics) using
|
||||
metrics exposed by the [GitLab exporter](../prometheus/gitlab_metrics.md#metrics-available).
|
||||
|
||||
## Creating the self monitoring project
|
||||
|
|
@ -58,7 +58,7 @@ The dashboard uses metrics available in
|
|||
|
||||
|
||||
You can also
|
||||
[create your own dashboards](../../../user/project/integrations/prometheus.md#defining-custom-dashboards-per-project).
|
||||
[create your own dashboards](../../../operations/metrics/dashboards/index.md#defining-custom-dashboards-per-project).
|
||||
|
||||
## Connection to Prometheus
|
||||
|
||||
|
|
@ -73,17 +73,17 @@ you should
|
|||
|
||||
## Taking action on Prometheus alerts **(ULTIMATE)**
|
||||
|
||||
You can [add a webhook](../../../user/project/integrations/prometheus.md#external-prometheus-instances)
|
||||
You can [add a webhook](../../../operations/metrics/index.md#external-prometheus-instances)
|
||||
to the Prometheus configuration in order for GitLab to receive notifications of any alerts.
|
||||
|
||||
Once the webhook is setup, you can
|
||||
[take action on incoming alerts](../../../user/project/integrations/prometheus.md#taking-action-on-incidents-ultimate).
|
||||
[take action on incoming alerts](../../../operations/metrics/index.md#taking-action-on-incidents-ultimate).
|
||||
|
||||
## Adding custom metrics to the self monitoring project
|
||||
|
||||
You can add custom metrics in the self monitoring project by:
|
||||
|
||||
1. [Duplicating](../../../user/project/integrations/prometheus.md#duplicating-a-gitlab-defined-dashboard) the default dashboard.
|
||||
1. [Duplicating](../../../operations/metrics/dashboards/index.md#duplicating-a-gitlab-defined-dashboard) the default dashboard.
|
||||
1. [Editing](../../../operations/metrics/dashboards/index.md#view-and-edit-the-source-file-of-a-custom-dashboard) the newly created dashboard file and configuring it with [dashboard YAML properties](../../../operations/metrics/dashboards/yaml.md).
|
||||
|
||||
## Troubleshooting
|
||||
|
|
|
|||
|
|
@ -317,7 +317,7 @@ migrations are completed (have an `up` status).
|
|||
|
||||
Sometimes you may need to re-import the common metrics that power the Metrics dashboards.
|
||||
|
||||
This could be as a result of [updating existing metrics](../../development/prometheus_metrics.md#update-existing-metrics), or as a [troubleshooting measure](../../user/project/integrations/prometheus.md#troubleshooting).
|
||||
This could be as a result of [updating existing metrics](../../development/prometheus_metrics.md#update-existing-metrics), or as a [troubleshooting measure](../../operations/metrics/dashboards/index.md#troubleshooting).
|
||||
|
||||
To re-import the metrics you can run:
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
|
|||
|
||||
## Select an environment
|
||||
|
||||
The **Environment** dropdown box above the dashboard displays the list of all [environments](../../../user/project/integrations/prometheus.md#monitoring-cicd-environments).
|
||||
The **Environment** dropdown box above the dashboard displays the list of all [environments](../index.md).
|
||||
It enables you to search as you type through all environments and select the one you're looking for.
|
||||
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ The options are:
|
|||
- [View logs](#view-logs-ultimate)
|
||||
- [Download CSV](#downloading-data-as-csv)
|
||||
- [Copy link to chart](../embed.md#embedding-gitlab-managed-kubernetes-metrics)
|
||||
- [Alerts](../../../user/project/integrations/prometheus.md#setting-up-alerts-for-prometheus-metrics)
|
||||
- [Alerts](../index.md#setting-up-alerts-for-prometheus-metrics)
|
||||
|
||||
### View and edit the source file of a custom dashboard
|
||||
|
||||
|
|
@ -123,3 +123,147 @@ You can create annotations by making requests to the
|
|||
To avoid excessive storage space consumption by stale annotations, records attached
|
||||
to time periods older than two weeks are removed daily. This recurring background
|
||||
job runs at 1:00 a.m. local server time.
|
||||
|
||||
## Add related links to custom dashboards
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216385) in GitLab 13.1.
|
||||
|
||||
You can embed links to other dashboards or external services in your custom
|
||||
dashboard by adding **Related links** to your dashboard's YAML file. Related links
|
||||
open in the same tab as the dashboard. Related links can be displayed in the
|
||||
following locations on your dashboard:
|
||||
|
||||
- At the top of your dashboard as the top level [`links` dashboard property](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties).
|
||||
- In charts context menus as the [`links` property of a panel](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties).
|
||||
|
||||
Related links can contain the following attributes:
|
||||
|
||||
- `url`: The full URL to the link. Required.
|
||||
- `title`: A phrase describing the link. Optional. If this attribute is not set,
|
||||
the full URL is used for the link title.
|
||||
- `type`: A string declaring the type of link. Optional. If set to `grafana`, the
|
||||
dashboard's time range values are converted to Grafana's time range format and
|
||||
appended to the `url`.
|
||||
|
||||
The dashboard's time range is appended to the `url` as URL parameters.
|
||||
|
||||
The following example shows two related links (`GitLab.com` and `GitLab Documentation`)
|
||||
added to a dashboard:
|
||||
|
||||
|
||||
|
||||
### Links Syntax
|
||||
|
||||
```yaml
|
||||
links:
|
||||
- title: GitLab.com
|
||||
url: https://gitlab.com
|
||||
- title: GitLab Documentation
|
||||
url: https://docs.gitlab.com
|
||||
- title: Public Grafana playground dashboard
|
||||
url: https://play.grafana.org/d/000000012/grafana-play-home?orgId=1
|
||||
type: grafana
|
||||
```
|
||||
|
||||
## Defining custom dashboards per project
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/59974) in GitLab 12.1.
|
||||
|
||||
By default, all projects include a GitLab-defined Prometheus dashboard, which
|
||||
includes a few key metrics, but you can also define your own custom dashboards.
|
||||
|
||||
You may create a new file from scratch or duplicate a GitLab-defined Prometheus
|
||||
dashboard.
|
||||
|
||||
NOTE: **Note:**
|
||||
The metrics as defined below do not support alerts, unlike
|
||||
[custom metrics](../index.md#adding-custom-metrics).
|
||||
|
||||
### Adding a new dashboard to your project
|
||||
|
||||
> UI option [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/223204) in GitLab 13.2.
|
||||
|
||||
You can configure a custom dashboard by adding a new YAML file into your project's
|
||||
`.gitlab/dashboards/` directory. In order for the dashboards to be displayed on
|
||||
the project's **{cloud-gear}** **Operations > Metrics** page, the files must have a `.yml`
|
||||
extension and should be present in the 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 **{cloud-gear}** **Operations > Metrics**.
|
||||
1. In the top-right corner of your dashboard, click the **{file-addition-solid}** **Actions** menu,
|
||||
and select **Create new**:
|
||||
|
||||
1. In the modal window, click **Open Repository**, then follow the instructions
|
||||
for creating a new dashboard from the command line.
|
||||
|
||||
To create a new dashboard from the command line:
|
||||
|
||||
1. Create `.gitlab/dashboards/prom_alerts.yml` under your repository's root
|
||||
directory. Each YAML file should define the layout of the dashboard and the
|
||||
Prometheus queries used to populate data. This example dashboard displays a
|
||||
single area chart:
|
||||
|
||||
```yaml
|
||||
dashboard: 'Dashboard Title'
|
||||
panel_groups:
|
||||
- group: 'Group Title'
|
||||
panels:
|
||||
- type: area-chart
|
||||
title: "Chart Title"
|
||||
y_label: "Y-Axis"
|
||||
y_axis:
|
||||
format: number
|
||||
precision: 0
|
||||
metrics:
|
||||
- id: my_metric_id
|
||||
query_range: 'http_requests_total'
|
||||
label: "Instance: {{instance}}, method: {{method}}"
|
||||
unit: "count"
|
||||
```
|
||||
|
||||
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
|
||||
dashboard from the dropdown.
|
||||
|
||||
NOTE: **Note:**
|
||||
Configuration files nested under subdirectories of `.gitlab/dashboards` are not
|
||||
supported and will not be available in the UI.
|
||||
|
||||
### Duplicating a GitLab-defined dashboard
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/37238) in GitLab 12.7.
|
||||
> - From [GitLab 12.8 onwards](https://gitlab.com/gitlab-org/gitlab/-/issues/39505), custom metrics are also duplicated when you duplicate a dashboard.
|
||||
|
||||
You can save a complete copy of a GitLab defined dashboard along with all custom metrics added to it.
|
||||
Resulting `.yml` file can be customized and adapted to your project.
|
||||
You can decide to save the dashboard `.yml` file in the project's **default** branch or in a
|
||||
new branch.
|
||||
|
||||
1. Click **Duplicate dashboard** in the dashboard dropdown or in the actions menu.
|
||||
|
||||
NOTE: **Note:**
|
||||
You can duplicate only GitLab-defined dashboards.
|
||||
|
||||
1. Enter the file name and other information, such as the new commit's message, and click **Duplicate**.
|
||||
|
||||
If you select your **default** branch, the new dashboard becomes immediately available.
|
||||
If you select another branch, this branch should be merged to your **default** branch first.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
When troubleshooting issues with a managed Prometheus app, it is often useful to
|
||||
[view the Prometheus UI](../../../development/prometheus.md#access-the-ui-of-a-prometheus-managed-application-in-kubernetes).
|
||||
|
||||
### "No data found" error on Metrics dashboard page
|
||||
|
||||
If the "No data found" screen continues to appear, it could be due to:
|
||||
|
||||
- No successful deployments have occurred to this environment.
|
||||
- Prometheus does not have performance data for this environment, or the metrics
|
||||
are not labeled correctly. To test this, connect to the Prometheus server and
|
||||
[run a query](../../../user/project/integrations/prometheus_library/kubernetes.md#metrics-supported), replacing `$CI_ENVIRONMENT_SLUG`
|
||||
with the name of your environment.
|
||||
- You may need to re-add the GitLab predefined common metrics. This can be done by running the [import common metrics Rake task](../../../administration/raketasks/maintenance.md#import-common-metrics).
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ Read the documentation on [templating](templating_variables.md).
|
|||
| `title` | string | no | Display title for the link. |
|
||||
| `type` | string | no | Type of the link. Specifies the link type, can be: `grafana` |
|
||||
|
||||
Read the documentation on [links](../../../user/project/integrations/prometheus.md#add-related-links-to-custom-dashboards).
|
||||
Read the documentation on [links](index.md#add-related-links-to-custom-dashboards).
|
||||
|
||||
## **Panel group (`panel_groups`) properties**
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ Panels in a panel group are laid out in rows consisting of two panels per row. A
|
|||
|
||||
| Property | Type | Required | Description |
|
||||
| ------ | ------ | ------ | ------ |
|
||||
| `id` | string | no | Used for associating dashboard metrics with database records. Must be unique across dashboard configuration files. Required for [alerting](../../../user/project/integrations/prometheus.md#setting-up-alerts-for-prometheus-metrics) (support not yet enabled, see [relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/27980)). |
|
||||
| `id` | string | no | Used for associating dashboard metrics with database records. Must be unique across dashboard configuration files. Required for [alerting](../index.md#setting-up-alerts-for-prometheus-metrics) (support not yet enabled, see [relevant issue](https://gitlab.com/gitlab-org/gitlab/-/issues/27980)). |
|
||||
| `unit` | string | yes | Defines the unit of the query's return data. |
|
||||
| `label` | string | no, but highly encouraged | Defines the legend-label for the query. Should be unique within the panel's metrics. Can contain time series labels as interpolated variables. |
|
||||
| `query` | string | yes if `query_range` is not defined | Defines the Prometheus query to be used to populate the chart/panel. If defined, the `query` endpoint of the [Prometheus API](https://prometheus.io/docs/prometheus/latest/querying/api/) will be utilized. |
|
||||
|
|
@ -128,3 +128,39 @@ metrics:
|
|||
This works by lowercasing the value of `label` and, if there are more words separated by spaces, replacing those spaces with an underscore (`_`). The transformed value is then checked against the labels of the time series returned by the Prometheus query. If a time series label is found that is equal to the transformed value, then the label value will be used and rendered in the legend like this:
|
||||
|
||||
|
||||
|
||||
## Dashboard YAML syntax validation
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33202) in GitLab 13.1.
|
||||
|
||||
To confirm your dashboard definition contains valid YAML syntax:
|
||||
|
||||
1. Navigate to **{doc-text}** **Repository > Files**.
|
||||
1. Navigate to your dashboard file in your repository.
|
||||
1. Review the information pane about the file, displayed above the file contents.
|
||||
|
||||
Files with valid syntax display **Metrics Dashboard YAML definition is valid**,
|
||||
and files with invalid syntax display **Metrics Dashboard YAML definition is invalid**.
|
||||
|
||||
|
||||
|
||||
When **Metrics Dashboard YAML definition is invalid** at least one of the following messages is displayed:
|
||||
|
||||
1. `dashboard: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties)
|
||||
1. `panel_groups: should be an array of panel_groups objects` [learn more](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties)
|
||||
1. `group: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-group-panel_groups-properties)
|
||||
1. `panels: should be an array of panels objects` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-group-panel_groups-properties)
|
||||
1. `title: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties)
|
||||
1. `metrics: should be an array of metrics objects` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties)
|
||||
1. `query: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `query_range: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `unit: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `YAML syntax: The parsed YAML is too big`
|
||||
|
||||
This is displayed when the YAML file is larger than 1 MB.
|
||||
|
||||
1. `YAML syntax: Invalid configuration format`
|
||||
|
||||
This is displayed when the YAML file is empty or does not contain valid YAML.
|
||||
|
||||
Metrics Dashboard YAML definition validation information is also available as a [GraphQL API field](../../../api/graphql/reference/index.md#metricsdashboard)
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ It is also possible to embed either the default dashboard metrics or individual
|
|||
|
||||
## Embedding metrics based on alerts in incident issues
|
||||
|
||||
For [GitLab-managed alerting rules](../../user/project/integrations/prometheus.md#setting-up-alerts-for-prometheus-metrics), the issue will include an embedded chart for the query corresponding to the alert. The chart displays an hour of data surrounding the starting point of the incident, 30 minutes before and after.
|
||||
For [GitLab-managed alerting rules](index.md#setting-up-alerts-for-prometheus-metrics), the issue will include an embedded chart for the query corresponding to the alert. The chart displays an hour of data surrounding the starting point of the incident, 30 minutes before and after.
|
||||
|
||||
For [manually configured Prometheus instances](../../user/project/integrations/prometheus.md#manual-configuration-of-prometheus), a chart corresponding to the query can be included if these requirements are met:
|
||||
|
||||
|
|
|
|||
|
|
@ -20,3 +20,110 @@ You can view the performance dashboard for an environment by [clicking on the mo
|
|||
You can set the visibility of the metrics dashboard to **Only Project Members**
|
||||
or **Everyone With Access**. When set to **Everyone with Access**, the metrics
|
||||
dashboard is visible to authenticated and non-authenticated users.
|
||||
|
||||
## Adding custom metrics
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3799) in [GitLab Premium](https://about.gitlab.com/pricing/) 10.6.
|
||||
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28527) to [GitLab Core](https://about.gitlab.com/pricing/) 12.10.
|
||||
|
||||
Custom metrics can be monitored by adding them on the monitoring dashboard page. Once saved, they will be displayed on the environment performance dashboard provided that either:
|
||||
|
||||
- A [connected Kubernetes cluster](../../user/project/clusters/add_remove_clusters.md) with the environment scope of `*` is used and [Prometheus installed on the cluster](../../user/project/integrations/prometheus.md#enabling-prometheus-integration)
|
||||
- Prometheus is [manually configured](../../user/project/integrations/prometheus.md#manual-configuration-of-prometheus).
|
||||
|
||||
|
||||
|
||||
A few fields are required:
|
||||
|
||||
- **Name**: Chart title
|
||||
- **Type**: Type of metric. Metrics of the same type will be shown together.
|
||||
- **Query**: Valid [PromQL query](https://prometheus.io/docs/prometheus/latest/querying/basics/).
|
||||
- **Y-axis label**: Y axis title to display on the dashboard.
|
||||
- **Unit label**: Query units, for example `req / sec`. Shown next to the value.
|
||||
|
||||
Multiple metrics can be displayed on the same chart if the fields **Name**, **Type**, and **Y-axis label** match between metrics. For example, a metric with **Name** `Requests Rate`, **Type** `Business`, and **Y-axis label** `rec / sec` would display on the same chart as a second metric with the same values. A **Legend label** is suggested if this feature is used.
|
||||
|
||||
## Editing additional metrics from the dashboard
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/208976) in GitLab 12.9.
|
||||
|
||||
You can edit existing additional custom metrics by clicking the **{ellipsis_v}** **More actions** dropdown and selecting **Edit metric**.
|
||||
|
||||
|
||||
|
||||
## Setting up alerts for Prometheus metrics
|
||||
|
||||
### Managed Prometheus instances
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/6590) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.2 for [custom metrics](#adding-custom-metrics), and 11.3 for [library metrics](../../user/project/integrations/prometheus_library/metrics.md).
|
||||
|
||||
For managed Prometheus instances using auto configuration, alerts for metrics [can be configured](#adding-custom-metrics) directly in the performance dashboard.
|
||||
|
||||
To set an alert:
|
||||
|
||||
1. Click on the ellipsis icon in the top right corner of the metric you want to create the alert for.
|
||||
1. Choose **Alerts**
|
||||
1. Set threshold and operator.
|
||||
1. Click **Add** to save and activate the alert.
|
||||
|
||||
|
||||
|
||||
To remove the alert, click back on the alert icon for the desired metric, and click **Delete**.
|
||||
|
||||
### External Prometheus instances
|
||||
|
||||
>- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9258) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.8.
|
||||
>- [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) to [GitLab Core](https://about.gitlab.com/pricing/) in 12.10.
|
||||
|
||||
For manually configured Prometheus servers, a notify endpoint is provided to use with Prometheus webhooks. If you have manual configuration enabled, an **Alerts** section is added to **Settings > Integrations > Prometheus**. This contains the *URL* and *Authorization Key*. The **Reset Key** button will invalidate the key and generate a new one.
|
||||
|
||||
|
||||
|
||||
To send GitLab alert notifications, copy the *URL* and *Authorization Key* into the [`webhook_configs`](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config) section of your Prometheus Alertmanager configuration:
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
name: gitlab
|
||||
webhook_configs:
|
||||
- http_config:
|
||||
bearer_token: 9e1cbfcd546896a9ea8be557caf13a76
|
||||
send_resolved: true
|
||||
url: http://192.168.178.31:3001/root/manual_prometheus/prometheus/alerts/notify.json
|
||||
...
|
||||
```
|
||||
|
||||
In order for GitLab to associate your alerts with an [environment](../../ci/environments/index.md), you need to configure a `gitlab_environment_name` label on the alerts you set up in Prometheus. The value of this should match the name of your Environment in GitLab.
|
||||
|
||||
NOTE: **Note**
|
||||
In GitLab versions 13.1 and greater, you can configure your manually configured Prometheus server to use the [Generic alerts integration](../../user/project/integrations/generic_alerts.md).
|
||||
|
||||
## Taking action on incidents **(ULTIMATE)**
|
||||
|
||||
>- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4925) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.11.
|
||||
>- [From GitLab Ultimate 12.5](https://gitlab.com/gitlab-org/gitlab/-/issues/13401), when GitLab receives a recovery alert, it will automatically close the associated issue.
|
||||
|
||||
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 > Incidents**.
|
||||
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.
|
||||
1. Click **Save changes**.
|
||||
|
||||
Once enabled, an issue will be opened automatically when an alert is triggered which contains values extracted from [alert's payload](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config):
|
||||
|
||||
- Issue author: `GitLab Alert Bot`
|
||||
- Issue title: Extract from `annotations/title`, `annotations/summary` or `labels/alertname`
|
||||
- Alert `Summary`: A list of properties
|
||||
- `starts_at`: Alert start time via `startsAt`
|
||||
- `full_query`: Alert query extracted from `generatorURL`
|
||||
- Optional list of attached annotations extracted from `annotations/*`
|
||||
- Alert [GFM](../../user/markdown.md): GitLab Flavored Markdown from `annotations/gitlab_incident_markdown`
|
||||
|
||||
When GitLab receives a **Recovery Alert**, it will automatically close the associated issue. This action will be recorded as a system message on the issue indicating that it was closed automatically by the GitLab Alert bot.
|
||||
|
||||
To further customize the issue, you can add labels, mentions, or any other supported [quick action](../../user/project/quick_actions.md) in the selected issue template, which will apply to all incidents. To limit quick actions or other information to only specific types of alerts, use the `annotations/gitlab_incident_markdown` field.
|
||||
|
||||
Since [version 12.2](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/63373), GitLab will tag each incident issue with the `incident` label automatically. If the label does not yet exist, it will be created automatically as well.
|
||||
|
||||
If the metric exceeds the threshold of the alert for over 5 minutes, an email will be sent to all [Maintainers and Owners](../../user/permissions.md#project-members-permissions) of the project.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ to create issues when alerts are triggered:
|
|||
checkbox to create an issue based on your own
|
||||
[issue templates](../project/description_templates.md#creating-issue-templates).
|
||||
For more information, see
|
||||
[Taking Action on Incidents](../project/integrations/prometheus.md#taking-action-on-incidents-ultimate) **(ULTIMATE)**.
|
||||
[Taking Action on Incidents](../../operations/metrics/index.md#taking-action-on-incidents-ultimate) **(ULTIMATE)**.
|
||||
1. To create issues from alerts, select the template in the **Issue Template**
|
||||
select box.
|
||||
1. To send [separate email notifications](#notify-developers-of-alerts) to users
|
||||
|
|
@ -36,7 +36,7 @@ to create issues when alerts are triggered:
|
|||
Appropriately configured alerts include an
|
||||
[embedded chart](../../operations/metrics/embed.md#embedding-metrics-based-on-alerts-in-incident-issues)
|
||||
for the query corresponding to the alert. You can also configure GitLab to
|
||||
[close issues](../project/integrations/prometheus.md#taking-action-on-incidents-ultimate)
|
||||
[close issues](../../operations/metrics/index.md#taking-action-on-incidents-ultimate)
|
||||
when you receive notification that the alert is resolved.
|
||||
|
||||
### Notify developers of alerts
|
||||
|
|
@ -53,8 +53,8 @@ To send separate email notifications to users with
|
|||
|
||||
You can set up Prometheus alerts in:
|
||||
|
||||
- [GitLab-managed Prometheus](../project/integrations/prometheus.md#setting-up-alerts-for-prometheus-metrics) installations.
|
||||
- [Self-managed Prometheus](../project/integrations/prometheus.md#external-prometheus-instances) installations.
|
||||
- [GitLab-managed Prometheus](../../operations/metrics/index.md#setting-up-alerts-for-prometheus-metrics) installations.
|
||||
- [Self-managed Prometheus](../../operations/metrics/index.md#external-prometheus-instances) installations.
|
||||
|
||||
Prometheus alerts are created by the special Alert Bot user. You can't remove this
|
||||
user, but it does not count toward your license limit.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ The entire payload will be posted in the issue discussion as a comment
|
|||
authored by the GitLab Alert Bot.
|
||||
|
||||
NOTE: **Note**
|
||||
In GitLab versions 13.1 and greater, you can configure [External Prometheus instances](prometheus.md#external-prometheus-instances) to use this endpoint.
|
||||
In GitLab versions 13.1 and greater, you can configure [External Prometheus instances](../../../operations/metrics/index.md#external-prometheus-instances) to use this endpoint.
|
||||
|
||||
## Setting up generic alerts
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ There are two ways to set up Prometheus integration, depending on where your app
|
|||
- For deployments on Kubernetes, GitLab can automatically [deploy and manage Prometheus](#managed-prometheus-on-kubernetes).
|
||||
- For other deployment targets, simply [specify the Prometheus server](#manual-configuration-of-prometheus).
|
||||
|
||||
Once enabled, GitLab will automatically detect metrics from known services in the [metric library](#monitoring-cicd-environments). You can also [add your own metrics](#adding-custom-metrics).
|
||||
Once enabled, GitLab will automatically detect metrics from known services in the [metric library](prometheus_library/index.md). You can also [add your own metrics](../../../operations/metrics/index.md#adding-custom-metrics).
|
||||
|
||||
## Enabling Prometheus Integration
|
||||
|
||||
|
|
@ -129,7 +129,7 @@ one of them will be used:
|
|||
[Prometheus manual configuration](#manual-configuration-of-prometheus)
|
||||
and a [managed Prometheus on Kubernetes](#managed-prometheus-on-kubernetes),
|
||||
the manual configuration takes precedence and is used to run queries from
|
||||
[dashboards](#defining-custom-dashboards-per-project) and [custom metrics](#adding-custom-metrics).
|
||||
[dashboards](../../../operations/metrics/dashboards/index.md#defining-custom-dashboards-per-project) and [custom metrics](../../../operations/metrics/index.md#adding-custom-metrics).
|
||||
- If you have managed Prometheus applications installed on Kubernetes clusters
|
||||
at **different** levels (project, group, instance), the order of precedence is described in
|
||||
[Cluster precedence](../../instance/clusters/index.md#cluster-precedence).
|
||||
|
|
@ -137,286 +137,6 @@ one of them will be used:
|
|||
clusters at the **same** level, the Prometheus application of a cluster with a
|
||||
matching [environment scope](../../../ci/environments/index.md#scoping-environments-with-specs) is used.
|
||||
|
||||
## Monitoring CI/CD Environments
|
||||
|
||||
Once configured, GitLab will attempt to retrieve performance metrics for any
|
||||
environment which has had a successful deployment.
|
||||
|
||||
GitLab will automatically scan the Prometheus server for metrics from known servers like Kubernetes and NGINX, and attempt to identify individual environments. The supported metrics and scan process is detailed in our [Prometheus Metrics Library documentation](prometheus_library/index.md).
|
||||
|
||||
You can view the performance dashboard for an environment by [clicking on the monitoring button](../../../ci/environments/index.md#monitoring-environments).
|
||||
|
||||
### Adding custom metrics
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3799) in [GitLab Premium](https://about.gitlab.com/pricing/) 10.6.
|
||||
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28527) to [GitLab Core](https://about.gitlab.com/pricing/) 12.10.
|
||||
|
||||
Custom metrics can be monitored by adding them on the monitoring dashboard page. Once saved, they will be displayed on the environment performance dashboard provided that either:
|
||||
|
||||
- A [connected Kubernetes cluster](../clusters/add_remove_clusters.md) with the environment scope of `*` is used and [Prometheus installed on the cluster](#enabling-prometheus-integration)
|
||||
- Prometheus is [manually configured](#manual-configuration-of-prometheus).
|
||||
|
||||
|
||||
|
||||
A few fields are required:
|
||||
|
||||
- **Name**: Chart title
|
||||
- **Type**: Type of metric. Metrics of the same type will be shown together.
|
||||
- **Query**: Valid [PromQL query](https://prometheus.io/docs/prometheus/latest/querying/basics/).
|
||||
- **Y-axis label**: Y axis title to display on the dashboard.
|
||||
- **Unit label**: Query units, for example `req / sec`. Shown next to the value.
|
||||
|
||||
Multiple metrics can be displayed on the same chart if the fields **Name**, **Type**, and **Y-axis label** match between metrics. For example, a metric with **Name** `Requests Rate`, **Type** `Business`, and **Y-axis label** `rec / sec` would display on the same chart as a second metric with the same values. A **Legend label** is suggested if this feature is used.
|
||||
|
||||
#### Editing additional metrics from the dashboard
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/208976) in GitLab 12.9.
|
||||
|
||||
You can edit existing additional custom metrics by clicking the **{ellipsis_v}** **More actions** dropdown and selecting **Edit metric**.
|
||||
|
||||
|
||||
|
||||
### Defining custom dashboards per project
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/59974) in GitLab 12.1.
|
||||
|
||||
By default, all projects include a GitLab-defined Prometheus dashboard, which
|
||||
includes a few key metrics, but you can also define your own custom dashboards.
|
||||
|
||||
You may create a new file from scratch or duplicate a GitLab-defined Prometheus
|
||||
dashboard.
|
||||
|
||||
NOTE: **Note:**
|
||||
The metrics as defined below do not support alerts, unlike
|
||||
[custom metrics](#adding-custom-metrics).
|
||||
|
||||
#### Adding a new dashboard to your project
|
||||
|
||||
> UI option [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/223204) in GitLab 13.2.
|
||||
|
||||
You can configure a custom dashboard by adding a new YAML file into your project's
|
||||
`.gitlab/dashboards/` directory. In order for the dashboards to be displayed on
|
||||
the project's **{cloud-gear}** **Operations > Metrics** page, the files must have a `.yml`
|
||||
extension and should be present in the 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](../../permissions.md#project-members-permissions).
|
||||
1. Navigate to your dashboard at **{cloud-gear}** **Operations > Metrics**.
|
||||
1. In the top-right corner of your dashboard, click the **{file-addition-solid}** **Actions** menu,
|
||||
and select **Create new**:
|
||||
|
||||
1. In the modal window, click **Open Repository**, then follow the instructions
|
||||
for creating a new dashboard from the command line.
|
||||
|
||||
To create a new dashboard from the command line:
|
||||
|
||||
1. Create `.gitlab/dashboards/prom_alerts.yml` under your repository's root
|
||||
directory. Each YAML file should define the layout of the dashboard and the
|
||||
Prometheus queries used to populate data. This example dashboard displays a
|
||||
single area chart:
|
||||
|
||||
```yaml
|
||||
dashboard: 'Dashboard Title'
|
||||
panel_groups:
|
||||
- group: 'Group Title'
|
||||
panels:
|
||||
- type: area-chart
|
||||
title: "Chart Title"
|
||||
y_label: "Y-Axis"
|
||||
y_axis:
|
||||
format: number
|
||||
precision: 0
|
||||
metrics:
|
||||
- id: my_metric_id
|
||||
query_range: 'http_requests_total'
|
||||
label: "Instance: {{instance}}, method: {{method}}"
|
||||
unit: "count"
|
||||
```
|
||||
|
||||
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
|
||||
dashboard from the dropdown.
|
||||
|
||||
NOTE: **Note:**
|
||||
Configuration files nested under subdirectories of `.gitlab/dashboards` are not
|
||||
supported and will not be available in the UI.
|
||||
|
||||
#### Duplicating a GitLab-defined dashboard
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/37238) in GitLab 12.7.
|
||||
> - From [GitLab 12.8 onwards](https://gitlab.com/gitlab-org/gitlab/-/issues/39505), custom metrics are also duplicated when you duplicate a dashboard.
|
||||
|
||||
You can save a complete copy of a GitLab defined dashboard along with all custom metrics added to it.
|
||||
Resulting `.yml` file can be customized and adapted to your project.
|
||||
You can decide to save the dashboard `.yml` file in the project's **default** branch or in a
|
||||
new branch.
|
||||
|
||||
1. Click **Duplicate dashboard** in the dashboard dropdown or in the actions menu.
|
||||
|
||||
NOTE: **Note:**
|
||||
You can duplicate only GitLab-defined dashboards.
|
||||
|
||||
1. Enter the file name and other information, such as the new commit's message, and click **Duplicate**.
|
||||
|
||||
If you select your **default** branch, the new dashboard becomes immediately available.
|
||||
If you select another branch, this branch should be merged to your **default** branch first.
|
||||
|
||||
#### Dashboard YAML syntax validation
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33202) in GitLab 13.1.
|
||||
|
||||
To confirm your dashboard definition contains valid YAML syntax:
|
||||
|
||||
1. Navigate to **{doc-text}** **Repository > Files**.
|
||||
1. Navigate to your dashboard file in your repository.
|
||||
1. Review the information pane about the file, displayed above the file contents.
|
||||
|
||||
Files with valid syntax display **Metrics Dashboard YAML definition is valid**,
|
||||
and files with invalid syntax display **Metrics Dashboard YAML definition is invalid**.
|
||||
|
||||
|
||||
|
||||
When **Metrics Dashboard YAML definition is invalid** at least one of the following messages is displayed:
|
||||
|
||||
1. `dashboard: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties)
|
||||
1. `panel_groups: should be an array of panel_groups objects` [learn more](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties)
|
||||
1. `group: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-group-panel_groups-properties)
|
||||
1. `panels: should be an array of panels objects` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-group-panel_groups-properties)
|
||||
1. `title: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties)
|
||||
1. `metrics: should be an array of metrics objects` [learn more](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties)
|
||||
1. `query: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `query_range: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `unit: can't be blank` [learn more](../../../operations/metrics/dashboards/yaml.md#metrics-metrics-properties)
|
||||
1. `YAML syntax: The parsed YAML is too big`
|
||||
|
||||
This is displayed when the YAML file is larger than 1 MB.
|
||||
|
||||
1. `YAML syntax: Invalid configuration format`
|
||||
|
||||
This is displayed when the YAML file is empty or does not contain valid YAML.
|
||||
|
||||
Metrics Dashboard YAML definition validation information is also available as a [GraphQL API field](../../../api/graphql/reference/index.md#metricsdashboard)
|
||||
|
||||
### Add related links to custom dashboards
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216385) in GitLab 13.1.
|
||||
|
||||
You can embed links to other dashboards or external services in your custom
|
||||
dashboard by adding **Related links** to your dashboard's YAML file. Related links
|
||||
open in the same tab as the dashboard. Related links can be displayed in the
|
||||
following locations on your dashboard:
|
||||
|
||||
- At the top of your dashboard as the top level [`links` dashboard property](../../../operations/metrics/dashboards/yaml.md#dashboard-top-level-properties).
|
||||
- In charts context menus as the [`links` property of a panel](../../../operations/metrics/dashboards/yaml.md#panel-panels-properties).
|
||||
|
||||
Related links can contain the following attributes:
|
||||
|
||||
- `url`: The full URL to the link. Required.
|
||||
- `title`: A phrase describing the link. Optional. If this attribute is not set,
|
||||
the full URL is used for the link title.
|
||||
- `type`: A string declaring the type of link. Optional. If set to `grafana`, the
|
||||
dashboard's time range values are converted to Grafana's time range format and
|
||||
appended to the `url`.
|
||||
|
||||
The dashboard's time range is appended to the `url` as URL parameters.
|
||||
|
||||
The following example shows two related links (`GitLab.com` and `GitLab Documentation`)
|
||||
added to a dashboard:
|
||||
|
||||
|
||||
|
||||
#### Links Syntax
|
||||
|
||||
```yaml
|
||||
links:
|
||||
- title: GitLab.com
|
||||
url: https://gitlab.com
|
||||
- title: GitLab Documentation
|
||||
url: https://docs.gitlab.com
|
||||
- title: Public Grafana playground dashboard
|
||||
url: https://play.grafana.org/d/000000012/grafana-play-home?orgId=1
|
||||
type: grafana
|
||||
```
|
||||
|
||||
### Setting up alerts for Prometheus metrics
|
||||
|
||||
#### Managed Prometheus instances
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/6590) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.2 for [custom metrics](#adding-custom-metrics), and 11.3 for [library metrics](prometheus_library/metrics.md).
|
||||
|
||||
For managed Prometheus instances using auto configuration, alerts for metrics [can be configured](#adding-custom-metrics) directly in the performance dashboard.
|
||||
|
||||
To set an alert:
|
||||
|
||||
1. Click on the ellipsis icon in the top right corner of the metric you want to create the alert for.
|
||||
1. Choose **Alerts**
|
||||
1. Set threshold and operator.
|
||||
1. Click **Add** to save and activate the alert.
|
||||
|
||||
|
||||
|
||||
To remove the alert, click back on the alert icon for the desired metric, and click **Delete**.
|
||||
|
||||
#### External Prometheus instances
|
||||
|
||||
>- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9258) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.8.
|
||||
>- [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42640) to [GitLab Core](https://about.gitlab.com/pricing/) in 12.10.
|
||||
|
||||
For manually configured Prometheus servers, a notify endpoint is provided to use with Prometheus webhooks. If you have manual configuration enabled, an **Alerts** section is added to **Settings > Integrations > Prometheus**. This contains the *URL* and *Authorization Key*. The **Reset Key** button will invalidate the key and generate a new one.
|
||||
|
||||
|
||||
|
||||
To send GitLab alert notifications, copy the *URL* and *Authorization Key* into the [`webhook_configs`](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config) section of your Prometheus Alertmanager configuration:
|
||||
|
||||
```yaml
|
||||
receivers:
|
||||
name: gitlab
|
||||
webhook_configs:
|
||||
- http_config:
|
||||
bearer_token: 9e1cbfcd546896a9ea8be557caf13a76
|
||||
send_resolved: true
|
||||
url: http://192.168.178.31:3001/root/manual_prometheus/prometheus/alerts/notify.json
|
||||
...
|
||||
```
|
||||
|
||||
In order for GitLab to associate your alerts with an [environment](../../../ci/environments/index.md), you need to configure a `gitlab_environment_name` label on the alerts you set up in Prometheus. The value of this should match the name of your Environment in GitLab.
|
||||
|
||||
NOTE: **Note**
|
||||
In GitLab versions 13.1 and greater, you can configure your manually configured Prometheus server to use the [Generic alerts integration](generic_alerts.md).
|
||||
|
||||
### Taking action on incidents **(ULTIMATE)**
|
||||
|
||||
>- [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/4925) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.11.
|
||||
>- [From GitLab Ultimate 12.5](https://gitlab.com/gitlab-org/gitlab/-/issues/13401), when GitLab receives a recovery alert, it will automatically close the associated issue.
|
||||
|
||||
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 > Incidents**.
|
||||
1. Enable the option to create issues.
|
||||
1. Choose the [issue template](../description_templates.md) to create the issue from.
|
||||
1. Optionally, select whether to send an email notification to the developers of the project.
|
||||
1. Click **Save changes**.
|
||||
|
||||
Once enabled, an issue will be opened automatically when an alert is triggered which contains values extracted from [alert's payload](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config):
|
||||
|
||||
- Issue author: `GitLab Alert Bot`
|
||||
- Issue title: Extract from `annotations/title`, `annotations/summary` or `labels/alertname`
|
||||
- Alert `Summary`: A list of properties
|
||||
- `starts_at`: Alert start time via `startsAt`
|
||||
- `full_query`: Alert query extracted from `generatorURL`
|
||||
- Optional list of attached annotations extracted from `annotations/*`
|
||||
- Alert [GFM](../../markdown.md): GitLab Flavored Markdown from `annotations/gitlab_incident_markdown`
|
||||
|
||||
When GitLab receives a **Recovery Alert**, it will automatically close the associated issue. This action will be recorded as a system message on the issue indicating that it was closed automatically by the GitLab Alert bot.
|
||||
|
||||
To further customize the issue, you can add labels, mentions, or any other supported [quick action](../quick_actions.md) in the selected issue template, which will apply to all incidents. To limit quick actions or other information to only specific types of alerts, use the `annotations/gitlab_incident_markdown` field.
|
||||
|
||||
Since [version 12.2](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/63373), GitLab will tag each incident issue with the `incident` label automatically. If the label does not yet exist, it will be created automatically as well.
|
||||
|
||||
If the metric exceeds the threshold of the alert for over 5 minutes, an email will be sent to all [Maintainers and Owners](../../permissions.md#project-members-permissions) of the project.
|
||||
|
||||
## Determining the performance impact of a merge
|
||||
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10408) in GitLab 9.2.
|
||||
|
|
@ -442,19 +162,3 @@ Performance data will be available for the duration it is persisted on the
|
|||
Prometheus server.
|
||||
|
||||
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
When troubleshooting issues with a managed Prometheus app, it is often useful to
|
||||
[view the Prometheus UI](../../../development/prometheus.md#access-the-ui-of-a-prometheus-managed-application-in-kubernetes).
|
||||
|
||||
### "No data found" error on Metrics dashboard page
|
||||
|
||||
If the "No data found" screen continues to appear, it could be due to:
|
||||
|
||||
- No successful deployments have occurred to this environment.
|
||||
- Prometheus does not have performance data for this environment, or the metrics
|
||||
are not labeled correctly. To test this, connect to the Prometheus server and
|
||||
[run a query](prometheus_library/kubernetes.md#metrics-supported), replacing `$CI_ENVIRONMENT_SLUG`
|
||||
with the name of your environment.
|
||||
- You may need to re-add the GitLab predefined common metrics. This can be done by running the [import common metrics Rake task](../../../administration/raketasks/maintenance.md#import-common-metrics).
|
||||
|
|
|
|||
|
|
@ -41,16 +41,16 @@ When GitLab-managed Prometheus is installed, the [Alerts list](#alert-management
|
|||
is also enabled.
|
||||
|
||||
To populate the alerts with data, see
|
||||
[GitLab-Managed Prometheus instances](../integrations/prometheus.md#managed-prometheus-instances).
|
||||
[GitLab-Managed Prometheus instances](../../../operations/metrics/index.md#managed-prometheus-instances).
|
||||
|
||||
### Enable external Prometheus alerts
|
||||
|
||||
You can configure an externally-managed Prometheus instance to send alerts
|
||||
to GitLab. To set up this configuration, see the [configuring Prometheus](../integrations/prometheus.md#external-prometheus-instances) documentation. Activating the external Prometheus
|
||||
to GitLab. To set up this configuration, see the [configuring Prometheus](../../../operations/metrics/index.md#external-prometheus-instances) documentation. Activating the external Prometheus
|
||||
configuration also enables the [Alerts list](#alert-management-list).
|
||||
|
||||
To populate the alerts with data, see
|
||||
[External Prometheus instances](../integrations/prometheus.md#external-prometheus-instances).
|
||||
[External Prometheus instances](../../../operations/metrics/index.md#external-prometheus-instances).
|
||||
|
||||
## Alert Management severity
|
||||
|
||||
|
|
@ -216,14 +216,14 @@ To view the metrics for an alert:
|
|||
|
||||
For GitLab-managed Prometheus instances, metrics data is automatically available
|
||||
for the alert, making it easy to see surrounding behavior. See
|
||||
[Managed Prometheus instances](../integrations/prometheus.md#managed-prometheus-instances)
|
||||
[Managed Prometheus instances](../../../operations/metrics/index.md#managed-prometheus-instances)
|
||||
for information on setting up alerts.
|
||||
|
||||
For externally-managed Prometheus instances, you can configure your alerting rules to
|
||||
display a chart in the alert. See
|
||||
[Embedding metrics based on alerts in incident issues](../../../operations/metrics/embed.md#embedding-metrics-based-on-alerts-in-incident-issues)
|
||||
for information on how to appropriately configure your alerting rules. See
|
||||
[External Prometheus instances](../integrations/prometheus.md#external-prometheus-instances)
|
||||
[External Prometheus instances](../../../operations/metrics/index.md#external-prometheus-instances)
|
||||
for information on setting up alerts for your self-managed Prometheus instance.
|
||||
|
||||
## Use cases for assigning alerts
|
||||
|
|
|
|||
Loading…
Reference in New Issue