0
LW created
Hi
We are experiencing an issue where exceptions are not being properly logged with their full details to Application Insights.
Problem: When an error occurs, we only see a generic error message in the logs, not the actual exception details or stack trace.
Example from Application Insights:
MessageTemplate: ---------- RemoteServiceErrorInfo ----------
{
"code": null,
"message": "Sisäinen virhe tapahtui pyynnön käsittelyssä.",
"details": null,
"data": null,
"validationErrors": null
}
RequestPath: /api/abp/application-localization
ActionName: Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationLocalizationController.GetAsync (Volo.Abp.AspNetCore.Mvc)
Expected behavior: We want to hide exception details from the client (for security), but still log the full exception with stack trace to Application Insights for debugging purposes.
Questions:
- Is there a built-in ABP configuration to log full exception details server-side while hiding them from clients?
- Are we missing any middleware or configuration that would enable detailed server-side logging?
- Do we need to implement a custom
IExceptionFilteror overrideIExceptionToErrorInfoConverter?
1 Answer(s)
-
0
hi
The
RemoteServiceErrorInfowill be shown for the front end.abp will also write the error logs when
RemoteServiceErrorInfohappens.You can check [Err] logs in the
logs.txtfileThanks.
