From 119d2c3d2e89038336c01ac43a511f55872e42f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kamil=20Trzci=C5=84ski?= Date: Wed, 5 Sep 2018 22:01:17 +0200 Subject: Update docs --- doc/development/prometheus_metrics.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') 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 -- cgit v1.2.3