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
Apache auto-instrumentation #1082
Conversation
672ed5d
to
9bd7f40
Compare
I would propose to split the PR into:
|
``` | ||
|
||
The Dockerfiles for auto-instrumentation can be found in [autoinstrumentation directory](./autoinstrumentation). | ||
Follow the instructions in the Dockerfiles on how to build a custom container image. | ||
|
||
>**Note:** For `Apache` auto-instrumentation, by default, instrumentation assumes httpd version 2.4. If you need to use version 2.2, or you need to adjust agent parameters, adjust instrumentation per following example: |
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.
This deserves a new section
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.
Hello Pavol,
thank you for your review. Based on you comments, I'd do a new set of PR's
- auto-instrumentation image build and documentation
- changes related to Instrumentation CRD - definition, validation, etc.
- Injection itself + e2e tests
- default settings in the operator
Would that be 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.
yes, that would be perfect ❤️
- manager.yaml |
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.
this needs to be reverted
no longer needed! #1236 did this |
PR proposes auto-instrumentation for applications running on Apache HTTPD server in K8S environment.
For instrumentation library, it uses https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/otel-webserver-module
For instrumentation itself, it adheres to the principles used for other languages already supported as much as possible.