You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When an Azure WebApp or similar service is instrumented with the .NET Agent, the agent logs are written to C:\home\logfiles as expected. But when you run the Azure Diagnostic Dump (via Kudu or elsewhere), you will get the profiler logs but not the agent logs.
Expected Behavior
Agent logs should be included in the diagnostic dump.
Additional context
This was introduced with the switch to Serilog for agent logging in v10.11.0. This Serilog issue suggests we might need to use the flushToDiskInterval parameter in our configuration.
For Maintainers Only or Hero Triaging this bug Suggested Priority (P1,P2,P3,P4,P5):
P3 Suggested T-Shirt size (S, M, L, XL, Unknown):
S
The text was updated successfully, but these errors were encountered:
Description
When an Azure WebApp or similar service is instrumented with the .NET Agent, the agent logs are written to
C:\home\logfiles
as expected. But when you run the Azure Diagnostic Dump (via Kudu or elsewhere), you will get the profiler logs but not the agent logs.Expected Behavior
Agent logs should be included in the diagnostic dump.
Additional context
This was introduced with the switch to Serilog for agent logging in v10.11.0. This Serilog issue suggests we might need to use the
flushToDiskInterval
parameter in our configuration.For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
P3
Suggested T-Shirt size (S, M, L, XL, Unknown):
S
The text was updated successfully, but these errors were encountered: