[chore] update references to loglevel (#8374)

These should have been updated some time ago when loglevel was replaced by verbosity. Signed-off-by: Alex Boten <aboten@lightstep.com>
open-telemetry · Sep 7, 2023 · 244ac13 · 244ac13
1 parent 8195e46
commit 244ac13
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/confmap/provider/internal/configurablehttpprovider/testdata/otel-config.yaml b/confmap/provider/internal/configurablehttpprovider/testdata/otel-config.yaml
@@ -21,7 +21,7 @@ processors:
 
 exporters:
   logging:
-    loglevel: debug
+    verbosity: detailed
 
 service:
   pipelines:

diff --git a/service/README.md b/service/README.md
@@ -6,7 +6,7 @@ The `--config` flag accepts either a file path or values in the form of a config
 Currently, the OpenTelemetry Collector supports the following providers `scheme`:
 - [file](../confmap/provider/fileprovider/provider.go) - Reads configuration from a file. E.g. `file:path/to/config.yaml`.
 - [env](../confmap/provider/envprovider/provider.go) - Reads configuration from an environment variable. E.g. `env:MY_CONFIG_IN_AN_ENVVAR`.
-- [yaml](../confmap/provider/yamlprovider/provider.go) - Reads configuration from yaml bytes. E.g. `yaml:exporters::logging::loglevel: debug`.
+- [yaml](../confmap/provider/yamlprovider/provider.go) - Reads configuration from yaml bytes. E.g. `yaml:exporters::logging::verbosity: detailed`.
 - [http](../confmap/provider/httpprovider/provider.go) - Reads configuration from a HTTP URI. E.g. `http://www.example.com`
 
 For more technical details about how configuration is resolved you can read the [configuration resolving design](../confmap/README.md#configuration-resolving).
@@ -32,9 +32,9 @@ For more technical details about how configuration is resolved you can read the
 
     `./otelcorecol --config=file:examples/local/otel-config.yaml --config=env:MY_OTHER_CONFIG`
 
-2. Merge a `config.yaml` file with the content of a yaml bytes configuration (overwrites the `exporters::logging::loglevel` config) and use the content as the config:
+2. Merge a `config.yaml` file with the content of a yaml bytes configuration (overwrites the `exporters::logging::verbosity` config) and use the content as the config:
 
-    `./otelcorecol --config=file:examples/local/otel-config.yaml --config="yaml:exporters::logging::loglevel: info"`
+    `./otelcorecol --config=file:examples/local/otel-config.yaml --config="yaml:exporters::logging::verbosity: normal"`
 
 ### Embedding other configuration providers