-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
doc(k8s-operator): document customizing enabled auto-instrumentations for nodejs with kubernetes-operator #4137
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @atsu85, please see my comment on updating the Node.JS documentation first, let me know if you have bandwidth to do the same as well.
@atsu85 any updates, can you take a look at my feedback? feel free to ask questions if you are unsure how to proceed |
beab727
to
31aa091
Compare
@svrnm, sorry for noticing this so late and thanks for the feedback. Please take a look, I hope my solution is OK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
31aa091
to
30c355a
Compare
30c355a
to
92478ad
Compare
FYI: amended commits to fix linting errors (only includes changes done by |
… for nodejs with kubernetes-operator Closes 4130
ad12e34
to
87a3835
Compare
@svrnm , please approve this PR again! I saw that Spelling check action was failing, because of |
Thank you @atsu85 |
The change
Current documentation states that it isn't possible to disable specific nodejs auto-instrumentation packages when using kubernetes-operator, but that isn't true after next kubernetes operator release, that allows enabling instrumentations based on
OTEL_NODE_ENABLED_INSTRUMENTATIONS
environment variable.[UPDATE:] Dependancy PRs released for now
This documentation change is caused by feature enabled by merged PR
that currently isn't released (hence the DRAFT status of this PR),
and another PR that built the foundation for it.