Commit c0b058c1 authored by Kati Paizee's avatar Kati Paizee

Merge branch 'am-add-instrumentation-class-usage-warning-to-docs' into 'master'

Update info note for instrumentation class usage

See merge request gitlab-org/gitlab!81892
parents 0c5944d5 2b1a4057
...@@ -26,13 +26,12 @@ To implement a new metric in Service Ping, follow these steps: ...@@ -26,13 +26,12 @@ To implement a new metric in Service Ping, follow these steps:
1. [Verify your metric](#verify-your-metric) 1. [Verify your metric](#verify-your-metric)
1. [Set up and test Service Ping locally](#set-up-and-test-service-ping-locally) 1. [Set up and test Service Ping locally](#set-up-and-test-service-ping-locally)
NOTE:
When you add or change a Service Metric, you must migrate metrics to [instrumentation classes](metrics_instrumentation.md).
For information about the progress on migrating Service ping metrics, see this [epic](https://gitlab.com/groups/gitlab-org/-/epics/5547).
## Instrumentation classes ## Instrumentation classes
Implementing metrics direct in `usage_data.rb` is deprecated, we recommend you use [instrumentation classes](metrics_instrumentation.md). NOTE:
Implementing metrics directly in `usage_data.rb` is deprecated.
When you add or change a Service Ping Metric, you must migrate metrics to [instrumentation classes](metrics_instrumentation.md).
For information about the progress on migrating Service Ping metrics, see this [epic](https://gitlab.com/groups/gitlab-org/-/epics/5547).
For example, we have the following instrumentation class: For example, we have the following instrumentation class:
`lib/gitlab/usage/metrics/instrumentations/count_boards_metric.rb`. `lib/gitlab/usage/metrics/instrumentations/count_boards_metric.rb`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment