add getting started config by zeitlinger · Pull Request #402 · open-telemetry/opentelemetry-configuration (original) (raw)
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple small points, but I'm happy to get this merged and iterate. Having a minimalist (only 45 lines!) config file probably makes this more approachable.
| The [examples](./examples) directory contains a variety of sample configuration files to help get started and illustrate useful patterns. The following are noteworthy: |
|---|
| - [getting-started.yaml](./examples/getting-started.yaml): A minimal configuration file to get started with declarative configuration. This is a good starting point if you are new to declarative configuration. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to work on naming / framing for these. sdk-config.yaml also describes itself as a good starting point.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sdk-config.yaml is a comprehensive starting point
that sounds like a slightly more advanced use case
Co-authored-by: Jack Berg 34418638+jack-berg@users.noreply.github.com
Co-authored-by: Jack Berg 34418638+jack-berg@users.noreply.github.com
Co-authored-by: Tobias Bachert github.dev.k9ps1@mail.tobiasbachert.com
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})