From b5168812a5ea7fb45c9122d1b1f1897022b366b3 Mon Sep 17 00:00:00 2001
From: Antonio Goncalves <antonio.goncalves@gmail.com>
Date: Thu, 2 Apr 2020 17:02:14 +0200
Subject: [PATCH] Adding log level

I think it's important to mention all the log levels. There are so many loggers that we might get confused (eg. TRACE vs FINEST, etc.)

Co-Authored-By: George Gastaldi <gegastaldi@gmail.com>
Co-Authored-By: David M. Lloyd <david.lloyd@redhat.com>
---
 docs/src/main/asciidoc/logging.adoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/src/main/asciidoc/logging.adoc b/docs/src/main/asciidoc/logging.adoc
index 93117ba4d7ff8..ec611c80285ae 100644
--- a/docs/src/main/asciidoc/logging.adoc
+++ b/docs/src/main/asciidoc/logging.adoc
@@ -54,6 +54,21 @@ The root logger category is handled separately, and is configured via the follow
 |quarkus.log.level|INFO|The default minimum log level for every log category.
 |===
 
+=== Log levels
+
+There are several log levels you can use:
+
+[cols="<m,<5",options="header"]
+|===
+|Level|Description
+|FATAL|A critical service failure/complete inability to service requests of any kind
+|ERROR|A significant disruption in a request or the inability to service a request
+|WARN|A non-critical service error or problem that may not require immediate correction
+|INFO|Service lifecycle events or important related very-low-frequency information
+|DEBUG|Messages that convey extra information regarding lifecycle or non-request-bound events which may be helpful for debugging
+|TRACE|Messages that convey extra per-request debugging information that may be very high frequency
+|===
+
 [id="format-string"]
 == Format String