Profiling timing out unless using debug logging #243
-
|
Very curious issue, and I'd appreciate some guidance on troubleshooting this. If I set up my project locally just by adding the package and Then, when I launch the profiler with the "Profile now" button from the Azure Portal, it says "Profiling is in progress" for about 18 minutes, then fails with "Profiling timeout. Refresh and try again". However, if I run the exact same app but with Debug logging enabled, see below, profiling succeeds within about 4 minutes. {
"Logging": {
"LogLevel": {
"Microsoft.ApplicationInsights.Profiler": "Debug"
}
}I get this exception: How can this be fixed? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Hi @Piedone , thanks for the feedback. I think you are going toward the right direction for troubleshooting, these 4 events need to success before profiler's actually gonna work:
It appears that the stopping process failed for some reason. Usually, this indicates that the uploader (an out of proc assembly) was somehow not located. Since you have the logging enabled already, looking for logging entries about locating uploader. According to the code here, you would want to check for logs around It could usually cause by some project setup issue or file system permission issue. Find out why the target assembly |
Beta Was this translation helpful? Give feedback.
-
|
Hey @Piedone I am glad to hear that the profiler works for you. See this for details about uploader not exist, it looks like you might have a similar project structure, and there is something to try: |
Beta Was this translation helpful? Give feedback.
Hi @Piedone , thanks for the feedback.
I think you are going toward the right direction for troubleshooting, these 4 events need to success before profiler's actually gonna work:
It appears that the stopping process failed for some reason.
Usually, this indicates that the uploader (an out of proc assembly) was somehow not located. Since you have the logging enabled already, looking for logging entries about locating uploader.
According to the code here, you would want to check for logs around
Locating uploader by locator. Priority: {priority}., and find out why the uploader doesn't exist on ne…