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: telemetry/README.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@ This allows meters and traces to use direct references to the underlying instrum
15
15
Create a basic OpenTelemetry configuration file which will send data to the local instance of Grafana LGTM:
16
16
17
17
```yaml
18
+
file_format: "1.0-rc.3"
18
19
resource:
19
20
attributes:
20
21
- name: service.name
@@ -24,15 +25,14 @@ tracer_provider:
24
25
processors:
25
26
- batch: # NOTE: you should use batch in production!
26
27
exporter:
27
-
otlp:
28
-
protocol: grpc
28
+
otlp_grpc:
29
29
endpoint: http://localhost:4317
30
30
31
31
meter_provider:
32
32
readers:
33
33
- pull:
34
34
exporter:
35
-
prometheus: # pushes directly to prometheus backend.
35
+
prometheus/development: # pushes directly to prometheus backend.
36
36
host: 0.0.0.0
37
37
port: 9464
38
38
# optional: include resource attributes as constant labels
@@ -51,23 +51,19 @@ logger_provider:
51
51
processors:
52
52
- batch:
53
53
exporter:
54
-
otlp:
55
-
protocol: grpc
54
+
otlp_grpc:
56
55
endpoint: http://localhost:4317
57
56
58
57
59
58
cosmos_extra:
60
-
trace_file: ""
61
-
metrics_file: ""
62
-
metrics_file_interval: ""
63
-
logs_file: ""
64
59
instrument_host: true
65
60
instrument_runtime: true
66
61
propagators:
67
62
- tracecontext
68
63
```
69
64
70
-
For a full list of configurable options see: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/examples/kitchen-sink.yaml
65
+
For a full list of configurable options see: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/examples/kitchen-sink.yaml.
66
+
NOTE: the go implementation may not support all options, so check the go [otelconf](https://pkg.go.dev/go.opentelemetry.io/contrib/otelconf) documentation carefully to see what is actually supported.
71
67
72
68
3. set the `OTEL_EXPERIMENTAL_CONFIG_FILE` environment variable to the path of the configuration file:
0 commit comments