CustomLogger | Simple File Logger for Unity

I have a Controller, which is called by external microservices using the ClientProxy.send<>() method, which sends a command that is recognized by the accompanying @MessagePattern decorator and executes that Controller function:

I stumbled across lost log messages in our environment.

We use an ELK Stack and logback with logstash-logback-encoder in our Java applications. To do structured queries we use LogstashMarkers to append structured arguments to the logs. In the case of the lost log messages it is a string, which contains a JSON.

Some of the log messages are lost completly. Not only the markers were not saved but the complete log message. They are not visible in Kibana. There are no errors in the logs of our application or the logstash server.

I could create an example repository with minimal code and published it at GitHub: https://github.com/seism0saurus/logging-issue

To run it, you need a logstash server and netcat. The logger in that project is configured to use a console appender, so we have a reference, what messages where really logged. Additionally there is one appender for a netcat server on localhost:8081 and one appender for the logstash server. Both have the same config. Only the address is different. So I'm quite sure that the message is send to the logstash server, if it is send to netcat.

Here is the code of the main class:

Is there a way to set up an object to dynamically generate values for keys? For example, I want obj.foo to console.log("foo"), obj.bar to console.log("bar"), etc.? I'm trying to make a custom logger where

I developed a kind of wrapper to make it work as a custom logger. I'm instantiating this class using @CustomLog Lombok annotation just to make it easier and cleaner. The tricky thing comes next: the idea behind this wrapper is to use a common logger (as org.slf4j.Logger) along with a custom monitor class that each time I call log.error(), the proper message gets logged in the terminal and the event is sent to my monitoring tool (Prometheus in this case).

To achieve this I did the following classes:

1. CustomLoggerFactory the factory called by Lombok to instantiate my custom logger.

I have an odata query builder class that I am using to build my odata string that is desterilising the result based on the object that called it.

I am working on my first NestJS application, which was working fine with hardcoded database connecting string in app.module.ts.

But then as per our requirements, I had to pick the database config values from environment files. For that, I followed the configuration documentation on the nestjs documentation website - https://docs.nestjs.com/techniques/configuration

But the issue is that I need to use the .env variables inside the same file for database connection, which is failing.

Here is my original code that was working fine:

I generate a spring boot project, and I want to log in an external file.

I choose to use Logback implementation, and here is my logback.xml file :

Context: I am trying to capture multiple events in our api using serilog and the elastic search sink, these events include: GET actions(regular web api flow) as well as login attempts (Owin). I am registering serilog like this:

I am trying to implement custom ILogger . NetCore 3.1