This repository was archived by the owner on Aug 3, 2024. It is now read-only.
Use TelemetryClient instead of SysDiag.Trace to trace AI initialization#319
Merged
xavierdecoster merged 1 commit intomasterfrom Nov 7, 2019
Merged
Use TelemetryClient instead of SysDiag.Trace to trace AI initialization#319xavierdecoster merged 1 commit intomasterfrom
xavierdecoster merged 1 commit intomasterfrom
Conversation
ryuyu
approved these changes
Nov 6, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I noticed we're missing traces from the
ApplicationInsights.Initializemethod.The following AI query returns zero results for e.g. EmailPublisher job:
Confirmed that these traces now do end up in AI.