Visão Geral
Um dos recursos que fazem parte do módulo LATROMI Essentials é o Visualizador de Eventos, onde podemos conferir ocorrências de erros, alertas de performance e informações de depuração.
Problema
Quando ocorre um erro de “Nenhum arquivo encontrado” no Extrator de Arquivos, o sistema registra apenas a mensagem e o Stack Trace do .NET. Informações importantes como Cód. de Atualização do Objeto, URL da requisição, não são registradas.
Exemplo:
Erro na execução do Pipeline
LATROMI.Core.Objects.FileExtractors.FileExtractorDomainException: Nenhum arquivo encontrado.
at LATROMI.Core.Objects.FileExtractors.Services.FileExtractorExecutor.<Execute>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LATROMI.Core.Objects.FileExtractors.Pipelining.FileExtractorExecutorPipelineTask.<InvokeAsync>d__5.MoveNext() in C:\Dados\DEV\LATROMI SVN\latromi-wecdb-trunk\src\Core\Modules\LowCode.FileExtractors\Domain\Pipelining\FileExtractorExecutorPipelineTask.cs:line 55
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LATROMI.Extensions.Objects.UseExtensions.<>c__DisplayClass5_1.<<UseActionInterface>b__1>d.MoveNext() in C:\Dados\DEV\LATROMI SVN\latromi-wecdb-trunk\src\Core\Modules\LowCode\Domain\Shared\Pipelining\Extensions\UseExtensions.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LATROMI.Core.Objects.Pipelining.Tasks.EventDispatcherPipelineTask.<InvokeAsync>d__0.MoveNext() in C:\Dados\DEV\LATROMI SVN\latromi-wecdb-trunk\src\Core\Modules\LowCode\Domain\Shared\Pipelining.Events\Tasks\EventDispatcherPipelineTask.cs:line 23
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LATROMI.Extensions.Objects.UseExtensions.<>c__DisplayClass5_1.<<UseActionInterface>b__1>d.MoveNext() in C:\Dados\DEV\LATROMI SVN\latromi-wecdb-trunk\src\Core\Modules\LowCode\Domain\Shared\Pipelining\Extensions\UseExtensions.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at LATROMI.Core.Objects.Shared.Pipelining.Tasks.ErrorHandlingPipelineTask.<InvokeAsync>d__3.MoveNext() in C:\Dados\DEV\LATROMI SVN\latromi-wecdb-trunk\src\Core\Modules\LowCode\Domain\Shared\Pipelining\Tasks\ErrorHandlingPipelineTask.cs:line 26
Solução
Implementar no Software, a gravação dos dados a seguir no log em questão:
- Cód. de Atualização do Objeto
- URL da requisição