-
Notifications
You must be signed in to change notification settings - Fork 237
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
Enable support for reusing plugins in multiple instances of AppInsights #1132
Labels
Comments
MSNev
pushed a commit
that referenced
this issue
Dec 6, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 6, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 10, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 13, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 13, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 16, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 17, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 18, 2019
MSNev
pushed a commit
that referenced
this issue
Dec 19, 2019
MSNev
added a commit
that referenced
this issue
Dec 19, 2019
Code is committed, will close the issue after we publish and official build (non-beta) with this change |
Version 2.4.3 is now published to CDN and NPM and addresses this enhancement |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Support to enable reusing the same plugin in different instances of AppInsights, owned by the same application (but using different Instrumentation keys) is required so that they can reuse a single Plugin instance for all instances.
Currently, while each AppInsights instance allows passing in extension plugins, internally this actually calls "initialize()" on each plugin for every instance, even if it's already been initialized.
Support for this requires 2 changes
The text was updated successfully, but these errors were encountered: