You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/maintenance/observability/metric-reporters.md
+35-7Lines changed: 35 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ reporters will be instantiated on each CoordinatorServer and TabletServers when
12
12
Example reporter configuration that specifies multiple reporters:
13
13
14
14
```yaml
15
-
metrics.reporters: jmx,prometheus
15
+
metrics.reporters: jmx,opentelemetry
16
16
```
17
17
18
18
## Push vs. Pull
@@ -57,6 +57,34 @@ An example for such a list would be `cluster_id=fluss1,host=localhost,server_id=
57
57
58
58
The domain thus identifies a metric class, while the key-property list identifies one (or multiple) instances of that metric.
59
59
60
+
### OpenTelemetry
61
+
62
+
Type: push
63
+
64
+
Parameters:
65
+
66
+
- `metrics.reporter.opentelemetry.endpoint`- Target to which the OpenTelemetry metric reporter is going to send metrics to.
67
+
- `metrics.reporter.opentelemetry.exporter` - The type of exporter that is used by the OpenTelemetry metric exporter to send metrics to the configured endpoint. The endpoint must accept connections for the given exporter type. Supported exporters: GRPC, HTTP.
68
+
- `metrics.reporter.opentelemetry.export-interval` - (optional) Frequency of metric export by the OpenTelemetry metric reporter to the endpoint. Default: 10s.
69
+
- `metrics.reporter.opentelemetry.export-timeout` - (optional) Maximum time the OpenTelemetry metric reporter will wait for each metric export. Default: 10s.
0 commit comments