Reid Morrison

Are you using structured logs (json format) into DataDog, or just the plain text logs? Highly recommend json logs, which break out all the data elements for you, the controller...

This is an example of how we switched our Kubernetes docker containers to log using json / structured logs. In `application.rb`: ~~~ruby # Setup structured logging config.semantic_logger.application = "my_app" config.semantic_logger.environment...

With Splunk and Observe, they both allow you to choose what columns are displayed. Strange that Data Dog is preventing you from being able to display the log event `name`...

Custom formatters can be supplied both via a proc and custom formatters that inherit from any of the out of the box formatters: https://logger.rocketjob.io/customize.html

Merged https://github.com/reidmorrison/rails_semantic_logger/pull/240 from @y-yagi

I believe others have done this by using something like this in the Gemfile: ~~~ruby gem "rails_semantic_logger", require: false ~~~ And then in the code, when we conditionally want to...

Looks good, can you try merging master again? Github won't let me fix the conflict myself.

Don't see much activity here anymore, have you tried [Semantic Logger](https://rocketjob.github.io/semantic_logger)? It has direct support for JRuby thread names, and also allows you to set your own thread names so...

Should not be too difficult to implement, the steps for someone that wants to submit a PR would be as follows: 1. Add `batch` method to HTTP Appender that like...

Let me know if you still see the warning after the PR was merged in `rails_semantic_logger` v 4.15.0.