-
Notifications
You must be signed in to change notification settings - Fork 417
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.
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 common usecases and recommended usage #688
Labels
Comments
Moving to GA milestone, as this is related to documentation. |
This issue was marked as stale due to lack of activity. It will be closed in 7 days if no furthur activity occurs. |
This issue was marked as stale due to lack of activity. It will be closed in 7 days if no furthur activity occurs. |
This issue was marked as stale due to lack of activity. It will be closed in 7 days if no furthur activity occurs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(came up during OpenTelemetry C++ SIG)
Creating this issue to track the common use-cases that we want to document in more detail. It would be ideal to add this documentation to readthedocs/Getting Started so that these common users can get started quickly without having to fully understand all the build options.
We can start in the roles defined in the specification here https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#user-roles
I've interpreted these roles to map to the use-cases of:
sdk
(and possibly install a vendor-specific)api
to instrument their application OR library codeapi
but is intended to be used by other applications (or libraries) and may be distributed by itselfsdk
and provides an SDK plugin that application owners can installPlease add comments for any use-cases that you may be interested in.
The text was updated successfully, but these errors were encountered: