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

NuGet packages: separate instrumentation packages for fine tuning deployment #2329

Closed
pjanotti opened this issue Mar 15, 2023 · 1 comment
Closed
Assignees
Milestone

Comments

@pjanotti
Copy link
Contributor

Application usage of the current NuGet package causes the deployment of all instrumentation-required packages with the application. As we grow the number of instrumentations this will get more visible. See the initial conversation here.

The proposed change is to separate the instrumentation packages and allow users concerned about deployment size to explicitly select the instrumentations that they are interested in.

Tangentially related to #1482.

@pjanotti
Copy link
Contributor Author

The mechanism and the larger offending packages were dealt with via #2554 - I'm going to close this issue and track separately any other instrumentation package that shouldn't be installed by default with the NuGet package.

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

No branches or pull requests

2 participants