Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document ability to use config providers inside config #7032

Merged
merged 3 commits into from
Jan 30, 2023
+21 −0
Merged

Document ability to use config providers inside config #7032

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fbd95c1
Document ability to use config providers inside config
jpkrohling Jan 26, 2023
f3988d7
s/file/provider/
jpkrohling Jan 26, 2023
22c4cac
Move to its own heading
jpkrohling Jan 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions service/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,25 @@ Currently, the OpenTelemetry Collector supports the following providers `scheme`

For more technical details about how configuration is resolved you can read the [configuration resolving design](../confmap/README.md#configuration-resolving).

One configuration file can also make references to other config providers, like the following:
jpkrohling marked this conversation as resolved.
Show resolved Hide resolved

```yaml
receivers:
otlp:
protocols:
grpc:

exporters: ${file:otlp-exporter.yaml}

service:
extensions: [ ]
pipelines:
traces:
receivers: [ otlp ]
processors: [ ]
exporters: [ otlp ]
```

### Single Config Source

1. Simple local file:
Expand Down