java-logging | If you are using Maven with BOM , add this to your pom | Build Tool library

I need to be able to log an Exception as a single record in my logs, which will make it much easier to investigate issues in Kibana / Elasticsearch. From what I can tell from the documentation for slf4j, the Logger interface requires messages to be Strings. Is my only option to remove newline characters from the Exception message before passing it to the Logger?

For context, I am using the following:

• .m2/repository/org/slf4j/slf4j-api/1.7.28/slf4j-api-1.7.28.jar
• Java 11
• Sprint Boot version 2.1.8.RELEASE

This is a trimmed down version of my custom exception handler :

I am new to java and trying to use the logger in java.util. I declare the logger like this snippet:

I'm trying to set up sending my application logs to Google Cloud Logging, but no matter what I try, the logs are not visible in the Log Viewer.

I tried:

• using the Java Logging Logback appender directly, following all of the steps in the documentation, setting different combinations of parameters
• using Spring Cloud GCP, again following all of the tutorials and trying different configurations
• using the CLI to write log entries, using the examples from the docs
• using the API explorer to write log entries, providing all of the required fields

The Log ingestion tab shows that the data is actually ingested and I am able to retrieve the entries using gcloud logging read or using the API explorer.

Unfortunately, the logs are not showing up in the viewer, which greets me with

[..] You do not have any logs in your project right now.

The logging API is, of course, enabled (I guess I wouldn't be able to get the CLI/API explorer to work without it).

Any clues what's wrong? Can it be that my logging entries have invalid format or are missing some key bit of information?

Attaching a couple of log entries, just in case. First was created by the API, second one was sent from the app:

We're having issues with our log4j2 configuration, which we've taken almost directly from https://www.baeldung.com/java-logging-rolling-file-appenders section 4.4:

I am learning to use spring webflux and as part of it i developed an application which uses Redis to save and retrieve data. But the problem i face is when the request tries to connect to redis i get following error :

I am using the SAP Cloud SDK to invoke OData service API_SALES_ORDER_SIMULATION_SRV to do sales order simulation.

The pay load I used is as below:

I am using a lambda function and writing it in Java. I was looking up logging for Lambda functions when I read the docs and they support log4j - http://docs.aws.amazon.com/lambda/latest/dg/java-logging.html#java-wt-logging-using-log4j.

I was wondering if we could use logging using the Slf4j annotation as well since Slf4j is only a binding annotation. Has anybody tried using Slf4j before with lambda?

I've tried to search on Spring documentation + articles on the internet + questions from Stackoverflow but I didn't find any information about it. For me the configuration of Log4J2 (especially the pattern) is much simpler, personal taste.

Also, I find that Log4J2 has better performance than Logback according to these articles:

https://stackify.com/compare-java-logging-frameworks

https://blog.overops.com/the-logging-olympics-a-race-between-todays-top-5-logging-frameworks

What is the difference between log4j, slf4j and logback?

https://www.sitepoint.com/which-java-logging-framework-has-the-best-performance/

And if we are to consider Async Logger, the performance is expediently higher in favor of Log4J2 according to Apache - https://logging.apache.org/log4j/2.x/performance.html and yes I know that it's their job to make their framework look better but I do believe that they are reliable.

My assumption is that Pivotal choose Logback to be the default because Log4J2 came sometime after they released version 1.0 of Spring-Boot.

Can anyone shed some light on this? Is my assumption correct?

I am trying to write a java based lambda function. Everything works fine except the logging. I have the log4j2.xml file in classpath.

I have also followed the instruction laid down in AWS Lambda LOgging in Java to the word.

I get this in the log when I trigger the Lambda function.

log4j:WARN No appenders could be found for logger (com.amazonaws.AmazonWebServiceClient). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

I use maven to package the jar. The pom.xml has the following dependencies.