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
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -286,7 +286,7 @@ private class IncludeRenderedMessageConverter : EventTelemetryConverter
286
286
### Or: Where did my Messages go?
287
287
288
288
As explained by
289
-
the [Application Insights documentation](https://azure.microsoft.com/en-us/documentation/articles/app-insights-api-custom-events-metrics/#flushing-data)
289
+
the [Application Insights documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/app/classic-api?tabs=dotnet#flushing-data)
290
290
, the default behaviour of the AI client is to buffer messages and send them to AI in batches whenever the client seems
291
291
fit. However, this may lead to lost messages when your application terminates while there are still unsent messages in
0 commit comments