logevents | extend implementation of SLF4J with batteries

After some research I found the Serilog.Formatting.Compact NuGet that will translate the Serilog LogEvent to a compact JSON string. This JSON string can then be read back into a Serilog LogEvent with Serilog-formatting-compact-reader NuGET. After some testing I can conclude that this works great.

There might be types that the JSON sterilizer can´t handle but I haven’t found any yet.

My best guess as to the cause of this problem is that calling Selenide.$("path").is(visible) causes a log event to be generated. This would cause your listener gets called again, so Selenide.$("path").is(visible) gets called again, which causes another log event, so your listener gets called again, and so on and so on until the stack overflows. However, I don't have enough of your stacktrace to be sure. I would be more sure of this problem if you could include the stacktrace down as far as the second line in which com.bme.listeners.EventLogger.beforeEvent appears.

What might help is adding a boolean field to your listener that records whether it is currently logging an event, and does nothing if beforeEvent is called and this field is true:

There are only two options here

• Use MyTcpServer in TcpServerSink but don't log to TcpServerSink
• Don't use MyTcpServer in TcpServerSink

For the first solution make MyTcpServer dependent on ILogger rather than using static Log dependency. This way you can pass whatever logger you want or just disable logging in your sink:

You don't need a grok pattern as your logs are in JSON format. Install logstash json filter plugin.

The Serilog configuration extension doesn't create instances of the sinks directly. All it does is to try to call a method .WriteTo.NameOfTheSinkYouDefinedInTheConfig(), if that exists - so for that to work, you need to provide this method yourself.

If you look at the source code of any of the official sinks, you'll notice that they are always declared as internal classes rather than public classes, and the way to hook sinks into the Serilog configuration is by creating an extension method to the LoggerSinkConfiguration class where you instantiate the sink yourself and add it to the pipeline.

In your case, it would be something like this:

I have a CloudWatch log-group-1, kinesis firehouse, lambda, S3.

log-group-1 sends logs to kinesis firehouse (using subscription filter). Kinesis firehouse triggers lambda to process the logs. Lambda returns the logs back to kinesis firehouse and kinesis firehouse saves transformed logs to S3.

Lambda gets the following input:

In order to bind to a property of an object you have to set the Path of the Binding to the name of the source property, while the source object is typically passed via the DataContext of the target object of the Binding.

For details, see Data binding overview on Microsoft Docs.

So replace

Thanks to Panagiotis Kanavos for making me aware of the Serilog self-logging.

I added the following into program.main, after the LoggerConfiguration:

IoT Hub will not accept the JSON in this form, because using the value true and adding it to a string will convert it to True (notice the upper case T). This is not a valid value for the JSON parser. Make sure the value you send is lower case.

While that will fix the exception, and fix your problem (IoT Hub will accept this text just fine), this is still not valid JSON. All the properties and string values should be surrounded by double-quotes. You want your JSON to end up looking like this: