We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oringally reported:microsoft/ApplicationInsights-aspnetcore#823 Application Insights Rejecting Exceptions with empty Message
Repro: TelemetryClient tc = new TelemetryClient(); tc.Context.InstrumentationKey = "validikey"; tc.TrackException(new Exception("")); tc.Flush();
Response from backend: Field 'message' on type 'ExceptionDetails' is required but missing or empty. Expected: string, Actual: undefined
// The following gets mesage automatically populated, but passing "" or string.empty breaks it. var ex = new Exception(); tc.TrackException(ex);
Fix would be to modify Exception sanitization to handle this properly.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Sorry, something went wrong.
This bug is still there.
This is still an issue, I've created a PR with a unit test: #2857 that will hopefully solve it.
No branches or pull requests
Oringally reported:microsoft/ApplicationInsights-aspnetcore#823
Application Insights Rejecting Exceptions with empty Message
Repro:
TelemetryClient tc = new TelemetryClient();
tc.Context.InstrumentationKey = "validikey";
tc.TrackException(new Exception(""));
tc.Flush();
Response from backend:
Field 'message' on type 'ExceptionDetails' is required but missing or empty. Expected: string, Actual: undefined
// The following gets mesage automatically populated, but passing "" or string.empty breaks it.
var ex = new Exception();
tc.TrackException(ex);
Fix would be to modify Exception sanitization to handle this properly.
The text was updated successfully, but these errors were encountered: