2 Configuring logging

ljacqu edited this page 2017-03-04 18:19:07 +01:00

Table of Contents

• Security.console.logConsole (true / false)
• settings.logLevel (INFO / FINE / DEBUG)

The configuration file config.yml contains two settings that influence the logging that AuthMe will perform.

Security.console.logConsole (true / false)

If set to true, everything that AuthMe logs to the console will also be saved in authme.log. If a technical error occurs (called Exception in Java), the full stacktrace is logged. This provides more technical details about the error, which are very interesting for us developers to know about.

settings.logLevel (INFO / FINE / DEBUG)

We recommend FINE. This logs, additionally to the INFO ones, some finer details which are still relevant and interesting to keep in a log. Use DEBUG if you're interested in seeing a lot of information from AuthMe. This is typically only used when you're trying to find the cause of an issue with AuthMe.

• Home
• For plugin users
  • AuthMe releases (Jenkins)
  • Breaking changes
  • Spawn handling
  • Name restrictions
  • Registration
  • Limbo players
  • Converters
  • Logging
  • Use Argon2
  • Forum integrations
  • Development team
  • Translators
  • Forge mods compatibility
  • 5.4 changelog
  • 5.3 changelog
  • 5.2 changelog
• For developers using AuthMe
  • Hooking into AuthMe
  • Plugins hooking into AuthMe
• For developers
  • Coding styleguide
  • Command handling
  • Dependency injection
  • Development setup
  • Limbo architecture
  • Tool tasks
  • Unit testing