This is the administration documentation. There is a separate [user documentation](../user/project/issues/managing_issues.md#closing-issues-automatically)
There is a separate [user documentation] on issue closing pattern.
on issue closing pattern.
When a commit or merge request resolves one or more issues, it is possible to
When a commit or merge request resolves one or more issues, it is possible to
automatically have these issues closed when the commit or merge request lands
automatically have these issues closed when the commit or merge request lands
...
@@ -13,8 +13,8 @@ in the project's default branch.
...
@@ -13,8 +13,8 @@ in the project's default branch.
In order to change the pattern you need to have access to the server that GitLab
In order to change the pattern you need to have access to the server that GitLab
is installed on.
is installed on.
The default pattern can be located in [`gitlab.yml.example`] under the
The default pattern can be located in [`gitlab.yml.example`](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example)
"Automatic issue closing" section.
under the "Automatic issue closing" section.
> **Tip:**
> **Tip:**
You are advised to use <http://rubular.com> to test the issue closing pattern.
You are advised to use <http://rubular.com> to test the issue closing pattern.
...
@@ -31,7 +31,7 @@ Because Rubular doesn't understand `%{issue_ref}`, you can replace this by
...
@@ -31,7 +31,7 @@ Because Rubular doesn't understand `%{issue_ref}`, you can replace this by
Available since [Omnibus GitLab 9.3](https://gitlab.com/gitlab-org/gitlab-ce/issues/29118). For
installations from source you'll have to configure it yourself.
installations from source you'll have to configure it yourself.
To enable the GitLab Prometheus metrics:
To enable the GitLab Prometheus metrics:
...
@@ -9,13 +9,13 @@ To enable the GitLab Prometheus metrics:
...
@@ -9,13 +9,13 @@ To enable the GitLab Prometheus metrics:
1. Log into GitLab as an administrator, and go to the Admin area.
1. Log into GitLab as an administrator, and go to the Admin area.
1. Click on the gear, then click on Settings.
1. Click on the gear, then click on Settings.
1. Find the `Metrics - Prometheus` section, and click `Enable Prometheus Metrics`
1. Find the `Metrics - Prometheus` section, and click `Enable Prometheus Metrics`
1.[Restart GitLab][restart] for the changes to take effect
1.[Restart GitLab](../../restart_gitlab.md#omnibus-gitlab-restart) for the changes to take effect
## Collecting the metrics
## Collecting the metrics
GitLab monitors its own internal service metrics, and makes them available at the
GitLab monitors its own internal service metrics, and makes them available at the
`/-/metrics` endpoint. Unlike other [Prometheus] exporters, in order to access
`/-/metrics` endpoint. Unlike other [Prometheus](https://prometheus.io) exporters, in order to access
it, the client IP needs to be [included in a whitelist][whitelist].
it, the client IP needs to be [included in a whitelist](../ip_whitelist.md).
For Omnibus and Chart installations, these metrics are automatically enabled and collected as of [GitLab 9.4](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1702). For source installations or earlier versions, these metrics will need to be enabled manually and collected by a Prometheus server.
For Omnibus and Chart installations, these metrics are automatically enabled and collected as of [GitLab 9.4](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/1702). For source installations or earlier versions, these metrics will need to be enabled manually and collected by a Prometheus server.
...
@@ -24,101 +24,101 @@ For Omnibus and Chart installations, these metrics are automatically enabled and
...
@@ -24,101 +24,101 @@ For Omnibus and Chart installations, these metrics are automatically enabled and
| gitlab_banzai_cached_render_real_duration_seconds | Histogram | 9.4 | Duration of rendering markdown into HTML when cached output exists | controller, action |
| `gitlab_banzai_cached_render_real_duration_seconds` | Histogram | 9.4 | Duration of rendering markdown into HTML when cached output exists | controller, action |
| gitlab_banzai_cacheless_render_real_duration_seconds | Histogram | 9.4 | Duration of rendering markdown into HTML when cached outupt does not exist | controller, action |
| `gitlab_banzai_cacheless_render_real_duration_seconds` | Histogram | 9.4 | Duration of rendering markdown into HTML when cached outupt does not exist | controller, action |
| geo_repositories | Gauge | 10.2 | Total number of repositories available on primary | url
| `geo_repositories` | Gauge | 10.2 | Total number of repositories available on primary | url |
| geo_repositories_synced | Gauge | 10.2 | Number of repositories synced on secondary | url
| `geo_repositories_synced` | Gauge | 10.2 | Number of repositories synced on secondary | url |
| geo_repositories_failed | Gauge | 10.2 | Number of repositories failed to sync on secondary | url
| `geo_repositories_failed` | Gauge | 10.2 | Number of repositories failed to sync on secondary | url |
| geo_lfs_objects | Gauge | 10.2 | Total number of LFS objects available on primary | url
| `geo_lfs_objects` | Gauge | 10.2 | Total number of LFS objects available on primary | url |
| geo_lfs_objects_synced | Gauge | 10.2 | Number of LFS objects synced on secondary | url
| `geo_lfs_objects_synced` | Gauge | 10.2 | Number of LFS objects synced on secondary | url |
| geo_lfs_objects_failed | Gauge | 10.2 | Number of LFS objects failed to sync on secondary | url
| `geo_lfs_objects_failed` | Gauge | 10.2 | Number of LFS objects failed to sync on secondary | url |
| geo_attachments | Gauge | 10.2 | Total number of file attachments available on primary | url
| `geo_attachments` | Gauge | 10.2 | Total number of file attachments available on primary | url |
| geo_attachments_synced | Gauge | 10.2 | Number of attachments synced on secondary | url
| `geo_attachments_synced` | Gauge | 10.2 | Number of attachments synced on secondary | url |
| geo_attachments_failed | Gauge | 10.2 | Number of attachments failed to sync on secondary | url
| `geo_attachments_failed` | Gauge | 10.2 | Number of attachments failed to sync on secondary | url |
| geo_last_event_id | Gauge | 10.2 | Database ID of the latest event log entry on the primary | url
| `geo_last_event_id` | Gauge | 10.2 | Database ID of the latest event log entry on the primary | url |
| geo_last_event_timestamp | Gauge | 10.2 | UNIX timestamp of the latest event log entry on the primary | url
| `geo_last_event_timestamp` | Gauge | 10.2 | UNIX timestamp of the latest event log entry on the primary | url |
| geo_cursor_last_event_id | Gauge | 10.2 | Last database ID of the event log processed by the secondary | url
| `geo_cursor_last_event_id` | Gauge | 10.2 | Last database ID of the event log processed by the secondary | url |
| geo_cursor_last_event_timestamp | Gauge | 10.2 | Last UNIX timestamp of the event log processed by the secondary | url
| `geo_cursor_last_event_timestamp` | Gauge | 10.2 | Last UNIX timestamp of the event log processed by the secondary | url |
| geo_status_failed_total | Counter | 10.2 | Number of times retrieving the status from the Geo Node failed | url
| `geo_status_failed_total` | Counter | 10.2 | Number of times retrieving the status from the Geo Node failed | url |
| geo_last_successful_status_check_timestamp | Gauge | 10.2 | Last timestamp when the status was successfully updated | url
| `geo_last_successful_status_check_timestamp` | Gauge | 10.2 | Last timestamp when the status was successfully updated | url |
| geo_lfs_objects_synced_missing_on_primary | Gauge | 10.7 | Number of LFS objects marked as synced due to the file missing on the primary | url
| `geo_lfs_objects_synced_missing_on_primary` | Gauge | 10.7 | Number of LFS objects marked as synced due to the file missing on the primary | url |
| geo_job_artifacts_synced_missing_on_primary | Gauge | 10.7 | Number of job artifacts marked as synced due to the file missing on the primary | url
| `geo_job_artifacts_synced_missing_on_primary` | Gauge | 10.7 | Number of job artifacts marked as synced due to the file missing on the primary | url |
| geo_attachments_synced_missing_on_primary | Gauge | 10.7 | Number of attachments marked as synced due to the file missing on the primary | url
| `geo_attachments_synced_missing_on_primary` | Gauge | 10.7 | Number of attachments marked as synced due to the file missing on the primary | url |
| geo_repositories_checksummed_count | Gauge | 10.7 | Number of repositories checksummed on primary | url
| `geo_repositories_checksummed_count` | Gauge | 10.7 | Number of repositories checksummed on primary | url |
| geo_repositories_checksum_failed_count | Gauge | 10.7 | Number of repositories failed to calculate the checksum on primary | url
| `geo_repositories_checksum_failed_count` | Gauge | 10.7 | Number of repositories failed to calculate the checksum on primary | url |
| geo_wikis_checksummed_count | Gauge | 10.7 | Number of wikis checksummed on primary | url
| `geo_wikis_checksummed_count` | Gauge | 10.7 | Number of wikis checksummed on primary | url |
| geo_wikis_checksum_failed_count | Gauge | 10.7 | Number of wikis failed to calculate the checksum on primary | url
| `geo_wikis_checksum_failed_count` | Gauge | 10.7 | Number of wikis failed to calculate the checksum on primary | url |
| geo_repositories_verified_count | Gauge | 10.7 | Number of repositories verified on secondary | url
| `geo_repositories_verified_count` | Gauge | 10.7 | Number of repositories verified on secondary | url |
| geo_repositories_verification_failed_count | Gauge | 10.7 | Number of repositories failed to verify on secondary | url
| `geo_repositories_verification_failed_count` | Gauge | 10.7 | Number of repositories failed to verify on secondary | url |
| geo_repositories_checksum_mismatch_count | Gauge | 10.7 | Number of repositories that checksum mismatch on secondary | url
| `geo_repositories_checksum_mismatch_count` | Gauge | 10.7 | Number of repositories that checksum mismatch on secondary | url |
| geo_wikis_verified_count | Gauge | 10.7 | Number of wikis verified on secondary | url
| `geo_wikis_verified_count` | Gauge | 10.7 | Number of wikis verified on secondary | url |
| geo_wikis_verification_failed_count | Gauge | 10.7 | Number of wikis failed to verify on secondary | url
| `geo_wikis_verification_failed_count` | Gauge | 10.7 | Number of wikis failed to verify on secondary | url |
| geo_wikis_checksum_mismatch_count | Gauge | 10.7 | Number of wikis that checksum mismatch on secondary | url
| `geo_wikis_checksum_mismatch_count` | Gauge | 10.7 | Number of wikis that checksum mismatch on secondary | url |
| geo_repositories_checked_count | Gauge | 11.1 | Number of repositories that have been checked via `git fsck` | url
| `geo_repositories_checked_count` | Gauge | 11.1 | Number of repositories that have been checked via `git fsck` | url |
| geo_repositories_checked_failed_count | Gauge | 11.1 | Number of repositories that have a failure from `git fsck` | url
| `geo_repositories_checked_failed_count` | Gauge | 11.1 | Number of repositories that have a failure from `git fsck` | url |
| geo_repositories_retrying_verification_count | Gauge | 11.2 | Number of repositories verification failures that Geo is actively trying to correct on secondary | url
| `geo_repositories_retrying_verification_count` | Gauge | 11.2 | Number of repositories verification failures that Geo is actively trying to correct on secondary | url |
| geo_wikis_retrying_verification_count | Gauge | 11.2 | Number of wikis verification failures that Geo is actively trying to correct on secondary | url
| `geo_wikis_retrying_verification_count` | Gauge | 11.2 | Number of wikis verification failures that Geo is actively trying to correct on secondary | url |