diff options
Diffstat (limited to 'doc/development/prometheus_metrics.md')
| -rw-r--r-- | doc/development/prometheus_metrics.md | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/development/prometheus_metrics.md b/doc/development/prometheus_metrics.md index a39d19d8750..8fcc025b35b 100644 --- a/doc/development/prometheus_metrics.md +++ b/doc/development/prometheus_metrics.md @@ -1,6 +1,6 @@ --- stage: Monitor -group: APM +group: Health info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers --- @@ -35,11 +35,6 @@ After you add or change an existing common metric, you must [re-run the import s Or, you can create a database migration: -NOTE: **Note:** -If a query metric (which is identified by `id:`) is removed it will not be removed from database by default. -You might want to add additional database migration that makes a decision what to do with removed one. -For example: you might be interested in migrating all dependent data to a different metric. - ```ruby class ImportCommonMetrics < ActiveRecord::Migration[4.2] include Gitlab::Database::MigrationHelpers @@ -56,6 +51,10 @@ class ImportCommonMetrics < ActiveRecord::Migration[4.2] end ``` +If a query metric (which is identified by `id:`) is removed it will not be removed from database by default. +You might want to add additional database migration that makes a decision what to do with removed one. +For example: you might be interested in migrating all dependent data to a different metric. + ## GitLab Prometheus metrics GitLab provides [Prometheus metrics](../administration/monitoring/prometheus/gitlab_metrics.md) |