Logging is a pretty crucial part of any application. The Masonite Logging package allows you to see errors your application is throwing as well as allow you to log your own messages in several different alert levels.
Masonite Logging currently contains the ability to log to a file, syslog and slack.
To get the Masonite Logging package up and running on your machine you must first install the package:
And then add the Service Provider to your application:
You can then publish the provider which will create your config/logging.py configuration file:
The Masonite Logging package will automatically register an exception listener with your Masonite application and log any exceptions your application encounters with the corresponding channel.
The Masonite Logging package uses the concept of channels and drivers. A channel internally is used to create and pass various information to instantiate the driver. At a higher level, you will mainly be working with channels.
Out of the box there are several different channels: single, stack, daily, slack, syslog and terminal. Each channel will handle logging messages in it's own way.
The single channel will put all information in a "single" file. This file can be specified in your config/logging.py file in the path option:
The daily channel is similiar to the single channel except this will create a new log file based on the current day. So this will create log files like 10-23-2019.log and 10-24-2019.log.
The path to set here needs to be a directory instead of a path to a file:
The Slack channel will send messages directly to your Slack channel so you or your team can act quickly and be alerted directly of any messages logged.
You'll need to generate a Slack application token. You can add it to your .env file:
You then need to set a few options in your config file if you need to change any default settings like the user, the icon emoji,
These options are up to you.
The terminal channel will simply output errors to the terminal. This is handy for debugging or in addition to other channels when using the stack channel.
The stack channel is useful when you need to combine several channels together. Maybe you want it to log to both a daily channel file as well as send a message to your slack group. You can do this easily by specifying the channels within your stack channel options.
You can have as many channels as you want here.
The syslog channel will tie directly into your system level logging software. Each operating system has its own type of system monitoring.
You'll need to tie into your system socket path. This can be different per operating system and machine so find yours and put that socket path in the config options:
Log levels are a hierarchy of log levels that you can specify on your channels. The hierarchy in order of most important to least important are:
Each channel can have its own minimum log level. The log message will only continue if it is greater than or equal to the minimum log level on that channel.
For example, if we have a configuration like this on the daily channel:
This will only send messages to this channel if the log level is notice or above. It will ignore all debug level log messages.
You can of course write your own log messages. You can resolve the logger class from the container and use a method equal to the log level you want to write the message for.
You can easily switch channels by using the channel method:
By default, Masonite Logging will record all times in the UTC timezone but in the event you want to switch timezones, you can do so in your configuration file:
All timestamps associated with logging will now use the correct timezone.