@@ -25,39 +25,42 @@ You can configure how internal metrics are generated and exposed by the
25
25
Collector. By default, the Collector generates basic metrics about itself and
26
26
exposes them using the OpenTelemetry Go
27
27
[ Prometheus exporter] ( https://github.com/open-telemetry/opentelemetry-go/tree/main/exporters/prometheus )
28
- for scraping at ` http://127.0.0.1:8888/metrics ` . You can expose the endpoint to
29
- one specific or all network interfaces when needed. For containerized
30
- environments, you might want to expose this port on a public interface.
28
+ for scraping at ` http://127.0.0.1:8888/metrics ` .
31
29
32
- Set the Prometheus config under ` service::telemetry::metrics ` :
30
+ The Collector can push its internal metrics to an OTLP
31
+ backend via the following configuration:
33
32
34
33
``` yaml
35
34
service :
36
35
telemetry :
37
36
metrics :
38
37
readers :
39
- - pull :
38
+ - periodic :
40
39
exporter :
41
- prometheus :
42
- host : ' 0.0.0.0 '
43
- port : 8888
40
+ otlp :
41
+ protocol : grpc/protobuf
42
+ endpoint : http://localhost:14317
44
43
` ` `
45
44
46
- Alternatively, the Collector can push its internal metrics via to an OTLP
47
- backend via the following configuration:
45
+ Alternatively, you can expose the Prometheus endpoint to
46
+ one specific or all network interfaces when needed. For containerized
47
+ environments, you might want to expose this port on a public interface.
48
+
49
+ Set the Prometheus config under ` service::telemetry::metrics`:
48
50
49
51
` ` ` yaml
50
52
service:
51
53
telemetry:
52
54
metrics:
53
55
readers:
54
- - periodic :
56
+ - pull :
55
57
exporter:
56
- otlp :
57
- protocol : grpc/protobuf
58
- endpoint : http://localhost:14317
58
+ prometheus :
59
+ host: '0.0.0.0'
60
+ port: 8888
59
61
` ` `
60
62
63
+
61
64
You can adjust the verbosity of the Collector metrics output by setting the
62
65
`level` field to one of the following values :
63
66
0 commit comments