Skip to content

Commit 871c749

Browse files
authored
docs: add note about metric name transformation (#1374)
Signed-off-by: Michael Beemer <[email protected]>
1 parent 239a432 commit 871c749

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

docs/reference/monitoring.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,17 +45,20 @@ Given below is the current implementation overview of flagd telemetry internals,
4545

4646
## Metrics
4747

48-
flagd expose following metrics,
48+
flagd exposes the following metrics:
4949

5050
- `http.server.duration`
5151
- `http.server.response.size`
5252
- `http.server.active_requests`
5353
- `feature_flag.flagd.impression`
5454
- `feature_flag.flagd.evaluation.reason`
5555

56+
> Please note that metric names may vary based on the consuming monitoring tool naming requirements.
57+
> For example, the transformation of OTLP metrics to Prometheus is described [here](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#otlp-metric-points-to-prometheus).
58+
5659
## Traces
5760

58-
flagd expose following traces,
61+
flagd creates the following spans as part of a trace:
5962

6063
- `flagEvaluationService(resolveX)` - SpanKind server
6164
- `jsonEvaluator(resolveX)` - SpanKind internal

0 commit comments

Comments
 (0)