From 9fd7f546414aa6620a2b6293f7f9203170eff50b Mon Sep 17 00:00:00 2001 From: ben69uaq Date: Tue, 12 Mar 2024 14:30:39 +0100 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20fix=20typo?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- content/en/docs/09.0/93_metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/09.0/93_metrics.md b/content/en/docs/09.0/93_metrics.md index 2665bbe4..4f684577 100644 --- a/content/en/docs/09.0/93_metrics.md +++ b/content/en/docs/09.0/93_metrics.md @@ -37,7 +37,7 @@ Let's test these impelementations in our producing application. ### {{% param sectionnumber %}}.1.1: Timer -We start by implementing a timer which tracks the time of our default `/data` endpoint to process a requst. We can simply annotate the function we want the timer to record with `@Timed` and the metric will be collected and exposed. Metrics will allow us to give them custom names, describe them and tag them for better readability. The annotation can be provided with the fields `value, description, extraTags` for this purpose. +We start by implementing a timer which tracks the time of our default `/data` endpoint to process a request. We can simply annotate the function we want the timer to record with `@Timed` and the metric will be collected and exposed. Metrics will allow us to give them custom names, describe them and tag them for better readability. The annotation can be provided with the fields `value, description, extraTags` for this purpose. Add the annotation to your endpoint and test your endpoint to see the result afterwards exposed to the `/q/metrics` endpoint.