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
…l developing.md & readme.md audits (#105)
<!--
Thank you for contributing to the project! 💜
Please see our [OSS process
document](https://github.com/honeycombio/home/blob/main/honeycomb-oss-lifecycle-and-practices.md#)
to get an idea of how we operate.
-->
## Which problem is this PR solving?
- Closes#57
- Closes#77
## Short description of the changes
- Created an examples overview
- Comments to smoke tests re: testing both configure_opentelemetry() and
opentelemetry_instrument
- Moved example development notes to developing.md
- Left additional breadcrumbs for others to use the smoke-test
docker-compose for running examples with collector should they so choose
## How to verify that this has the expected result
All the links in the readme's work.
Finding information about example usage is clear.
It's clear there are two ways to use the distro:
configure_opentelemetry() or opentelemetry_instrument
Note: This is probably best reviewed by viewing the readme's in the
[repo
view](https://github.com/honeycombio/honeycomb-opentelemetry-python/tree/emash-config-vs-command)
rather than the .md diffs :)
Ensure docs describe both auto and manual SDK configuration using the distro.
For example:
opentelemetry-instrument
configure_opentelemetry
Note: our hello-world-flask example only show auto instrumentation.
The text was updated successfully, but these errors were encountered: