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

Publisher ApplicationInsights to use active TmetryConfiguration #465

Merged

Conversation

SpaceOgre
Copy link
Contributor

What this PR does / why we need it:
As discused in #426 this PR changes HealthChecks.Publisher.ApplicationInsights to use the active TelemetryConfiguration instead of just the active instrumentation key. This change means that ITelemetryInitializers (and other changes to the active configuration) that are add are used for AI events as well.

Which issue(s) this PR fixes:
#426

Does this PR introduce a user-facing change?:
Yes, if for some reason a user don't want the extra configurations they have done for AI then they would now need to manually supply the instrumentation key.

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Unit tests passing
  • End-to-end tests passing
  • Extended the documentation
  • Provided sample for the feature

…metryConfiguration instead of just active instrumentation key
@unaizorrilla unaizorrilla merged commit f6a0873 into Xabaril:master Mar 30, 2020
@unaizorrilla
Copy link
Collaborator

LGTM

@unaizorrilla
Copy link
Collaborator

Hi @SpaceOgre
Thanks for contribute this. When the release build finished a new package 3.0.4 will be on Nuget,

@sungam3r sungam3r mentioned this pull request Jul 30, 2023
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.

2 participants