Exceptions with high line number in the stacktrace are dropped.

[Daniel-Guenter]

It seems like I cannot track an exception that has an unusually high line number in the stack trace. The exception never shows up in the application insights backend. The stack trace may contain this.

{ "level":2, "method":"Data.Entities.General.TransactionLogEntry.set_CustomerIP", "assembly":"Data, Version=2.1.2.0, Culture=neutral, PublicKeyToken=null", "line":16707560 },

Turning on AI debug logging shows this message.

Microsoft.ApplicationInsights.Extensibility.TraceSource Warning: 71 : TransmissionDataLossError. Telemetry items are being lost here as the response code is not in the whitelisted set of retriable codes.TransmissionId: xxxxxxxxx=. Status Code: 400.

A fiddler trace shows this.

It looks like if the line on a stack trace is greater that 1000000 the upload will fail. The reason the line numbers are so high is that this code is generated by Postsharp, an AOP library and it uses these numbers for it's own debugger plugin.

I was thinking I could write a processor to sanitize this data, but the data I need to access ExceptionDetails, StackFrame are both internal.

Can this limit be increased, or can the data be sanitized so that exception is not lost?

[Daniel-Guenter]

Can we get this linked with the pull request 2497 that fixes this issue?