Spring Boot Applications 59. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

Spring Boot Applications 59. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform following example: %clr(%5p) The mapping of log level to a color is as follows: Level Color FATAL Red ERROR Red WARN Yellow Level Color INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

.................................................................................... 199 59.3. OpenShift ............................................................................................... following example: %clr(%5p) The mapping of log level to a color is as follows: Level Color FATAL Red ERROR Red WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify the color blue • cyan • faint • green Spring Boot Reference Guide 2.0.0.M6 Spring Boot 75 • magenta • red • yellow 26.3 File Output By default, Spring Boot logs only to the console and does not write log

Spring Boot Applications 61. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

Spring Boot Applications 60. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

.................................................................................... 230 60.3. OpenShift ............................................................................................... %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify the color • cyan • faint • green • magenta Spring Boot Reference Guide 2.0.4.RELEASE Spring Boot 80 • red • yellow 26.3 File Output By default, Spring Boot logs only to the console and does not write log

Spring Boot Applications 60. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

Spring Boot Applications 62. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

Spring Boot Applications 61. Deploying to the Cloud Cloud Foundry Binding to Services Heroku OpenShift Amazon Web Services (AWS) AWS Elastic Beanstalk Using the Tomcat Platform Using the Java SE Platform %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red Level Color WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify HH:mm:ss.SSS}){yellow} The following colors and styles are supported: blue cyan faint green magenta red yellow File Output By default, Spring Boot logs only to the console and does not write log files

.................................................................................... 209 59.3. OpenShift ............................................................................................... %clr(%5p) The following table describes the mapping of log levels to colors: Level Color FATAL Red ERROR Red WARN Yellow INFO Green DEBUG Green TRACE Green Alternatively, you can specify the color blue • cyan • faint • green Spring Boot Reference Guide 2.0.0.RC1 Spring Boot 76 • magenta • red • yellow 26.3 File Output By default, Spring Boot logs only to the console and does not write log