JSON Template Layout - level - short name

[amosshi]

In the document it reads:

• https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-pattern

If you find yourself using pattern, it is highly likely you are either doing something wrong, or JSON Template Layout needs some improvement.

In our current settings, we do use pattern for the log level, which generates only 1 character to save disk space, and somewhat readable, like

• I for INFO
• W for WARN
• E for ERROR

  "logLevel": {
    "$resolver": "pattern",
    "pattern": "%level{length=1}"
  }

In today's JSON Template Layout, we do have another option of severity / code, which will generate a number for level based on Syslog severity, like

• 6 for INFO
• 4 for WARN
• 3 for ERROR

config         = field , [ severity ]
field          = "field" -> ( "name" | "severity" )
severity       = severity-field
severity-field = "field" -> ( "keyword" | "code" )

Well it is clear the severity code (4, 5, 6) is NOT reader friendly and we need a mapping to make it readable.

The Request

• It will be perfect JSON Template Layout can natively support the single character level

[vy]

@amosshi, thanks so much for sharing this feedback.

to save disk space

Would you mind sharing a little bit more detail about your deployment setup, please? I presume you don't have a log ingestion system, e.g., ELK, in this particular case, but plain files storing JSON one-liners. Do you have file compression enabled, and yet still observe significant improvement after switching to single-character setup? Have you considered using custom layouts (e.g., SMILE-encoding) or compression-enabled solutions (e.g., YScope's CLP Appender)? If yes, where do they fall short?