-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Meta] Add missing "Using instrumentation libraries" pages #4319
Comments
Hey @svrnm |
hey @devc007, thanks for your interest in that matter. While learning about c++ instrumentation you can also help us by making the existing documentation on other pages better as well, so everything we have already under https://opentelemetry.io/docs/languages/cpp/, when you feel comfortable enough feel free to come up with a basic page for this issue. From what I know there are no C++ instrumentation libraries yet and I am also not 100% sure if this is even applicable for C++ like in other languages, so we might need to discuss this when you know more. |
@svrnm |
C++ might be not that trivial to take on if there are no instrumentation libraries yet (as far as I am aware of), so the page might be fairly stub and calling out that instrumentation libraries might be built in the future.
There is none probably for the same reason |
Working on the Python one! Also doing PHP and Erlang. Might edit the Swift one later for structure. |
@devc007 feel free to take the PRs for reference when doing the C++ one |
@devc007 We only need the C++ to close this one. Could you take another look at the comments? Thanks! |
All done now. :) |
Across all languages we need a page with linkTitle "libraries", title "Using instrumentation libraries" that speaks about instrumentation of dependencies either via native/out of the box instrumentation OR instrumentation libraries.
The following language specific pages exist already and can be used as template:
The following are still missing:
If you want to contribute to this issue, comment, mention the language that you want to use and then provide a PR accordingly
The text was updated successfully, but these errors were encountered: