@@ -609,10 +609,9 @@ Collector issues. It consists of two subsections: `logs` and `metrics`.
609
609
The `logs` subsection lets you configure how the logs can be generated by the
610
610
Collector. By default, the Collector writes its logs to `stderr` with a log
611
611
level of `INFO`. You can also add static key-value pairs to all log entries with
612
- the `initial_fields` to enrich the logging context. As per the `LogsConfig`
613
- defined in v{{%
614
- param vers %}} [here](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
615
- param vers %}}/service/telemetry/config.go), the `logs` configuration options are :
612
+ the `initial_fields` to enrich the logging context. The [`logs` configuration
613
+ options](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
614
+ param vers %}}/service/telemetry/config.go) are :
616
615
617
616
- `level` : sets the minimum enabled logging level, default `INFO`.
618
617
- `development` : puts the logger in development mode, default `false`.
@@ -635,17 +634,16 @@ The `metrics` subsection lets you configure how the metrics can be generated and
635
634
exposed by the Collector. By default, the Collector generates basic metrics
636
635
about itself and expose them for scraping at <http://127.0.0.1:8888/metrics>.
637
636
You can expose the endpoint to a specific or even all network interfaces when
638
- needed. As per the `MetricsConfig` defined in v{{%
639
- param vers %}} [here](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
640
- param vers %}}/service/telemetry/config.go), the `metrics` configuration options
641
- are :
637
+ needed. The [`metrics` configuration
638
+ options](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{%
639
+ param vers %}}/service/telemetry/config.go) are :
642
640
643
641
- `level` : the level of telemetry metrics, default `basic`. The possible values
644
642
are :
645
- - " none" indicates that no telemetry data should be collected.
646
- - " basic" is the recommended and covers the basics of the service telemetry.
647
- - " normal" adds some other indicators on top of basic.
648
- - " detailed" adds dimensions and views to the previous levels .
643
+ - ` none` : no telemetry is collected.
644
+ - ` basic` : essential service telemetry.
645
+ - ` normal` : the default level, adds standard indicators on top of basic.
646
+ - ` detailed` : the most verbose level, includes dimensions and views .
649
647
- `address` : the `[address]:port` formatted URL that metrics exposition should
650
648
be bound to. Default `127.0.0.1:8888`.
651
649
@@ -858,7 +856,7 @@ Install [`cfssl`](https://github.com/cloudflare/cfssl) and create the following
858
856
859
857
Then run the following commands :
860
858
861
- ` ` ` bash
859
+ ` ` ` sh
862
860
cfssl genkey -initca csr.json | cfssljson -bare ca
863
861
cfssl gencert -ca ca.pem -ca-key ca-key.pem csr.json | cfssljson -bare cert
864
862
` ` `
@@ -880,14 +878,14 @@ define with this method are merged into the final configuration after all
880
878
881
879
The following examples show how to override settings inside nested sections :
882
880
883
- ` ` ` shell
884
- # The following example sets the verbosity
885
- # level of the debug exporter to 'detailed'
881
+ ` ` ` sh
886
882
otelcol --set "exporters::debug::verbosity=detailed"
887
- # The following example overrides gRPC
888
- # settings for the OTLP receiver
889
883
otelcol --set "receivers::otlp::protocols::grpc={endpoint:localhost:4317, compression: gzip}"
890
884
` ` `
891
885
892
- Note tha the `--set` option doesn't support setting a key that contains a dot or
893
- an equal sign.
886
+ {{% alert title="Important" color="warning" %}}
887
+
888
+ The `--set` option doesn't support setting a key that contains a dot or an equal
889
+ sign.
890
+
891
+ {{% /alert %}}
0 commit comments