Skip to content
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

.NET - enable bytecode instrumentation #1081

Merged
merged 4 commits into from
Sep 15, 2022
Merged

.NET - enable bytecode instrumentation #1081

merged 4 commits into from
Sep 15, 2022

Conversation

Kielek
Copy link
Contributor

@Kielek Kielek commented Sep 8, 2022

Enables bytecode instrumentations. All of them are enabled by default.
For v.0.3.1-beta.1 it extends set of supported libraries: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/v0.3.1-beta.1/docs/config.md#instrumented-traces-libraries-and-frameworks

@Kielek Kielek marked this pull request as ready for review September 13, 2022 08:54
@Kielek Kielek requested a review from a team September 13, 2022 08:54
@Kielek
Copy link
Contributor Author

Kielek commented Sep 13, 2022

@open-telemetry/dotnet-instrumentation-approvers FYI

@Kielek
Copy link
Contributor Author

Kielek commented Sep 13, 2022

@avadhut123pisal, FYI

pkg/instrumentation/dotnet.go Show resolved Hide resolved
pkg/instrumentation/dotnet.go Show resolved Hide resolved
@pavolloffay pavolloffay merged commit 7700851 into open-telemetry:main Sep 15, 2022
@pellared
Copy link
Member

@Kielek I think it MAY be good to offer an easy way to disable byte-code instrumentation (disable attaching the .NET Profiler) as this can have negative consequences on the instrumented application's performance (maybe it was not enabled by default on purpose?)

@Kielek Kielek deleted the dotnet-enable-bytecode-instrumentation branch September 15, 2022 12:10
@Kielek
Copy link
Contributor Author

Kielek commented Sep 15, 2022

@Kielek I think it MAY be good to offer an easy way to disable byte-code instrumentation (disable attaching the .NET Profiler) as this can have negative consequences on the instrumented application's performance (maybe it was not enabled by default on purpose?)

My perspective is to offer as broad auto-instrumentation as possible.
It can be disabled by the user by setting CORECLR_ENABLE_PROFILING to 0.

ItielOlenick pushed a commit to ItielOlenick/opentelemetry-operator that referenced this pull request May 1, 2024
* .NET Auto Instrumentation - support for byte code instrumentation

* extract method to set env variable

* code review feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants