{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/azure-functions-host/issues/3213","repository_url":"https://api.github.com/repos/Azure/azure-functions-host","labels_url":"https://api.github.com/repos/Azure/azure-functions-host/issues/3213/labels{/name}","comments_url":"https://api.github.com/repos/Azure/azure-functions-host/issues/3213/comments","events_url":"https://api.github.com/repos/Azure/azure-functions-host/issues/3213/events","html_url":"https://github.com/Azure/azure-functions-host/issues/3213","id":346208763,"node_id":"MDU6SXNzdWUzNDYyMDg3NjM=","number":3213,"title":"Immediately flush fatal exceptions to App Insights","user":{"login":"brettsam","id":1089915,"node_id":"MDQ6VXNlcjEwODk5MTU=","avatar_url":"https://avatars2.githubusercontent.com/u/1089915?v=4","gravatar_id":"","url":"https://api.github.com/users/brettsam","html_url":"https://github.com/brettsam","followers_url":"https://api.github.com/users/brettsam/followers","following_url":"https://api.github.com/users/brettsam/following{/other_user}","gists_url":"https://api.github.com/users/brettsam/gists{/gist_id}","starred_url":"https://api.github.com/users/brettsam/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brettsam/subscriptions","organizations_url":"https://api.github.com/users/brettsam/orgs","repos_url":"https://api.github.com/users/brettsam/repos","events_url":"https://api.github.com/users/brettsam/events{/privacy}","received_events_url":"https://api.github.com/users/brettsam/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-31T14:18:11Z","updated_at":"2018-08-23T13:42:13Z","closed_at":null,"author_association":"MEMBER","body":"Since App Insights batches-and-flushes telemetry and also has a fire-and-forget mechanism for flushing, we can't be guaranteed that messages have made it to the service before we kill the process.\r\n\r\nWe may be able to implement something similar to this comment for things like the \"Host thresholds exceeded\" message: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/407#issuecomment-318208844."},"comment":{"url":"https://api.github.com/repos/Azure/azure-functions-host/issues/comments/415418239","html_url":"https://github.com/Azure/azure-functions-host/issues/3213#issuecomment-415418239","issue_url":"https://api.github.com/repos/Azure/azure-functions-host/issues/3213","id":415418239,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNTQxODIzOQ==","user":{"login":"JasonBSteele","id":1202763,"node_id":"MDQ6VXNlcjEyMDI3NjM=","avatar_url":"https://avatars0.githubusercontent.com/u/1202763?v=4","gravatar_id":"","url":"https://api.github.com/users/JasonBSteele","html_url":"https://github.com/JasonBSteele","followers_url":"https://api.github.com/users/JasonBSteele/followers","following_url":"https://api.github.com/users/JasonBSteele/following{/other_user}","gists_url":"https://api.github.com/users/JasonBSteele/gists{/gist_id}","starred_url":"https://api.github.com/users/JasonBSteele/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JasonBSteele/subscriptions","organizations_url":"https://api.github.com/users/JasonBSteele/orgs","repos_url":"https://api.github.com/users/JasonBSteele/repos","events_url":"https://api.github.com/users/JasonBSteele/events{/privacy}","received_events_url":"https://api.github.com/users/JasonBSteele/received_events","type":"User","site_admin":false},"created_at":"2018-08-23T13:42:13Z","updated_at":"2018-08-23T13:42:13Z","author_association":"NONE","body":"Agreed, there should be an implicit Flush for fatal Exceptions. But I believe this should also apply to caught ones explicitly logged with TraceException. Exceptions will hopefully be rare and are very important to capture, and if debugging, see promptly so I think the overhead of flushing them is worth it against the usefulness of getting them quickly."}}
{"actor":{"display_login":"JasonBSteele"}}