summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorKamil Trzciński <ayufan@ayufan.eu>2018-09-05 22:01:17 +0200
committerKamil Trzciński <ayufan@ayufan.eu>2018-09-05 22:01:17 +0200
commit119d2c3d2e89038336c01ac43a511f55872e42f9 (patch)
treeff258058920546ca5e03a3d328620e782c6488d2 /doc
parent1471bee6d483bd5b795457c54e6de2f3c22145c1 (diff)
downloadgitlab-ce-119d2c3d2e89038336c01ac43a511f55872e42f9.tar.gz
Update docs
Diffstat (limited to 'doc')
-rw-r--r--doc/development/prometheus_metrics.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/development/prometheus_metrics.md b/doc/development/prometheus_metrics.md
index 6977815a979..b6b6d9665ea 100644
--- a/doc/development/prometheus_metrics.md
+++ b/doc/development/prometheus_metrics.md
@@ -6,8 +6,7 @@ We strive to support the 2-4 most important metrics for each common system servi
### Query identifier
-The requirement for adding a new metrics is to make each query to have an unique identifier.
-Identifier is used to update the metric later when changed.
+The requirement for adding a new metric is to make each query to have an unique identifier which is used to update the metric later when changed:
```yaml
- group: Response metrics (NGINX Ingress)
@@ -25,9 +24,10 @@ Identifier is used to update the metric later when changed.
After you add or change existing _common_ metric you have to create a new database migration that will query and update all existing metrics.
-**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.**
+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