When I attempted to enable Serilog.Sinks.Seq, I got the following exception on startup.
Unhandled exception. System.TypeInitializationException: The type initializer for 'Ice.Hosting.AspNetCore.StartupHelper' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Epicor.Hosting.Trace.ServerLog' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'Serilog.Sinks.Seq, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'Serilog.Sinks.Seq, Culture=neutral, PublicKeyToken=null'
I tried dropping the latest version of Serilog.Sinks.Seq into the,
Server\Assemblies
Server\Bin
Server\Customization\Externals
folders and still was not able to get it to find the assembly to load.
Not sure if I am missing something or am trying to do the impossible.
You would need to drop the correct version of the serilog DLL in the folder (specifically, the same version as the other serilog DLLs) You are also probably going to have to do a recycle on the application pool. It should work, unless there are additional missing dependencies…
I’ve been trying this out this morning, and sure there’s lots of information here.
I would mainly want to be logging the exceptions. I’m not seeing anywhere in the portal where an exception is logged.
There doesn’t seam to be anywhere in the application insights portal where this exception is visible.
In fact, I’m not seeing anywhere where the response code is anything but success! Response time matches though.
Nice work. Having the Epicor logs accessible in Seq will make trouble shooting easier. I am going to try this out on our Test environment.
A note of caution, Seq likes to use ram so watch out for that. I had an instance that took all the available ram until we limited it. Just searching now looks like the memory management in Seq has changed so that may no longer be an issue.
Apparently you can set the logging level (at least I see this in the Task agent help). So I’m assuming that in the host.config you might be able to override the logging level from verbose.