Activities of "BobIngham"

bump***

@wizgod, UserFriendlyException is designed to return an error message to the client. If you're throwing it in a Hangfire job there is no client, use standard exception handling or simply log the error.

Code was refactored, I am closing this issue to save anyone spending time on it.

Hi @ismcagdas, Ok, I hear what you're saying. At the moment I'm up to my ears trying to feed my logs into Sumo Logic. Once I'm done I may be to reach out and see if I can filter out these types of erros as exceptions in the end solution. Can we leave this item as open and I will revert when I know more.

Because the user has left open the system in the browser or has entered an incorrect password. In a large system this happens so often that it is extremely difficult to find exceptions thrown by the system as a result of cose error.

@demimursa, I stand corrected but flummoxed as to why a 401 should be considered as an exception, it's a user error not a system error. Can anypone throw any light on this?

@demirmusa, Forgive my ignorance. Why is a 401 reported as an exception?

Hi @demimursa, We seem to be using exception to handle programming flow. Let me give a simple example. I want to oursource the support of my system to a third party. One of the things this out-sourcing company will do is to check HTTP 500 errors and report them back to me. At the moment it is not possible to monitor HTTP 500 errors with Zero because the error log is full of exceptions such as "wrong password" and "token expired". These are not exceptions and should not be handled as such. So, I have to order my out-sourcing company to ignore exceptions because 99.5% of them are not actually exceptions: Failed login and token expired should both be warnings at best. And, moreover, as I said, this is a production system. Am I supposed to trace each exception back to the user and find out if they were redirected to the login page? The following issues would address the problem to some extent, they have all been on the backlog for months. Silent refresh token for JWT Session lock screen User lockout

I can confirm that this is a problem. Here is a screen shot of Application Insights from my Azure production system. my logs are written direct to Application Insights and not to text file.... I am currently trying to reduce exceptions in my logs, can someone advise accordingly?

Thanks.