Linux<\/h4>\nsudo php composer.phar require monolog\/monolog<\/pre>\nWindows<\/h4>\ncomposer require monolog\/monolog<\/pre>\nIn case you are not using composer, download the PSR-3 source code<\/strong> and install to your application.<\/p>\nMake sure that you are using namespaces (to avoid a headache) so that you don\u2019t require a lot of files.<\/p>\n
<\/a>Create loggers<\/h3>\nFirst, when you create a logger, channel name should be included, so that you can distinguish your list of loggers.<\/p>\n
$logger = new MonologLogger('channel-name');\n$app->container->logger = $logger;<\/pre>\nIn the example above, \u2018channel-name\u2019 should be included in every log entry. This way you can easily look up and filter the entries; createanother channel for each component. Examples of these channels might include \u2018database\u2019, \u2018security\u2019, \u2019business\u2019, and others.<\/p>\n
Loggers by nature don\u2019t know how to handle logs, but we also have what are called handlers that can handle logs.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\n\n$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/app.log', Logger::DEBUG));\n$logger->info('This is a log! ^_^ ');\n$logger->warning('This is a log warning! ^_^ ');\n$logger->error('This is a log error! ^_^ ');\n\n<\/pre>\nIf you are using PHP 7.4 you will need to use this slightly modified code:<\/p>\n
require __DIR__ . '\/vendor\/autoload.php';<\/pre>\nuse Monolog\\Handler\\StreamHandler;<\/pre>\nuse Monolog\\Logger;<\/pre>\n$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(__DIR__ . '\/app.log', Logger::DEBUG));<\/pre>\nHandlers can be pushed as many as you need to a Logger instance. These types of handler will decide the kind of logs to be handled. In the example provided above, StreamHandler, reports entries in the file system app.log.<\/p>\n
<\/a>Intensity level<\/h3>\nAn intensity level is added to each log entry, along with channel name to allow you to check and filter the entries.<\/p>\n
As illustrated in RFC 5424<\/strong> which describes the syslog protocol, the following levels of intensity are applied in Monolog.<\/p>\n\n- DEBUG<\/strong>: Detailed debugging information.<\/li>\n
- INFO<\/strong>: Handles normal events. Example: SQL logs<\/li>\n
- NOTICE<\/strong>: Handles normal events, but with more important events<\/li>\n
- WARNING<\/strong>: Warning status, where you should take an action before it will become an error.<\/li>\n
- ERROR<\/strong>: Error status, where something is wrong and needs your immediate action<\/li>\n
- CRITICAL<\/strong>: Critical status. Example: System component is not available<\/li>\n
- ALERT<\/strong>: Immediate action should be exercised. This should trigger some alerts and wake you up during night time.<\/li>\n
- EMERGENCY<\/strong>: It is used when the system is unusable.<\/li>\n<\/ul>\n
An info log entry of a channel called \u2018channel-name\u2019, for example, looks like this:<\/p>\n
[2018-07-05 11:10:35] channel-name.INFO: This is a log entry!\n[2018-07-09 02:58:27] channel-name.WARNING: This is a log warning! ^_^ [] []\n[2018-07-09 02:58:27] channel-name.ERROR: This is a log error! ^_^ [] []<\/pre>\nMonolog stores one add for each type of intensity level, likely, error, notice, warning, info, and so on.<\/p>\n
<\/a>PHP example code<\/h3>\nThe following code is the basic sample setup to log to a file and to firephp on the Debug level.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerFirePHPHandler;\n\n$logger = new Logger('logger');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test_app.log', Logger::DEBUG));\n$logger->pushHandler(new FirePHPHandler());\n$logger->error('Logger is now Ready');<\/pre>\nIn the sample, it has two handlers in the stack to provide records in two different ways. FirePHPHandlers are described as it is joined on top of the stack. This permits you to tentatively append a logger with bubbling disabled, if you want to revoke other configured loggers.<\/p>\n
<\/a>Handler order<\/h3>\nWhen you add a log entry handler to the logger instance, it matters which order you push the handler. When a log entry is added, it will directly go to the handler stack. When a handler’s constructor is set to false, it stops traversing through the handler stack.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerSwiftMailerHandler;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.example.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword('123456');\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['example-FROM@example.com' => 'Someone FROM']);\n$message->setTo(['someone-TO@example.com' => 'SomeoneTO']);\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushHandler(new SwiftMailerHandler($mailer, $message, Logger::CRITICAL, false));\n$logger->addCritical('Hey, a critical log entry!');<\/pre>\n![\"log\"](\"https:\/\/stackify.com\/wp-content\/uploads\/2018\/07\/word-image-44.png\")
<\/p>\n
First, you need to install SwiftMailer (composer require swiftmailer\/swiftmailer) to be able to use the SwiftMailerHandler. For you to be able to send emails, you need to use Swift_SmtpTransport, Swift_Message, and Swift_Mailer to join $mailer and $message to the SwiftMailerHandler instance.<\/p>\n
When you examine the last parameter of SwiftMailer’s constructor, it returns false for the last parameter, called $bubble parameter. Technically, by default, it returns true, but when set to false it means that it stops traversing the handler stack. This is a technique in which making the StreamHandler that is located at the bottom of the stack; it never store logs in the file system if SwiftMailerHandler manages the entry.<\/p>\n
<\/a>Array<\/h3>\nArray passing is as simple as the following code:<\/p>\n
$username = 'jmendez';\n$logger->addInfo('User registered', ['username' => $username]);<\/pre>\nThis is a way to pass an array to the add method such as addDebug, addInfo, etc.<\/p>\n
<\/a>Processors<\/h3>\nIn Monolog, you can create your own processor even though it provides a lot of processors by default. Processors are used to include information in log entries such as client’s IP and browser, and others. Here’s a sample code snippet:<\/p>\n
$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(function ($entry) {\n $entry['extra']['data'] = 'Hello world!';\n return $entry;\n});\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\nThe sample above would simply store the log entry in this format<\/p>\n
[2018-07-05 11:18:29] default.INFO: User registered {'username':'jmendez'} {\"data\":\"Hello world!\"}<\/pre>\nYou can also use the built-in processor that Monolog provides. You directly use the class and push an instance using the pushProcessor method. Here is sample code using pushProcessor.<\/p>\n
use MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologProcessorWebProcessor;\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(new WebProcessor());\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\n<\/a>Formatters<\/h3>\nIn Monolog, there are a lot of formatters that can be used. You can find some built-in formatters here<\/a>. You can also customize the format of the logs that are written in files, emails, databases, and other handlers.<\/p>\n$record['formatted']<\/pre>\nis the most common way to use a handler with a value to be directly put into the log device. Formatters can be customized, so you can write your own. Here is a simple configuration for a built-in formatter class that formats the log sent by email, which can be understandable by everyone who will be using your system.<\/p>\n
use MonologLogger;\nuse MonologHandlerSwiftMailerHandler;\nuse MonologFormatterHtmlFormatter;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.gmail.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword(123456);\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['fromuser@example.com' => 'From User']);\n$message->setTo(['touser@example.com' => 'To User']);\n$message->setContentType(\"text\/html\");\n\n$logger = new Logger('default');\n$mailerHandler = new SwiftMailerHandler($mailer, $message, Logger::CRITICAL);\n$mailerHandler->setFormatter(new HtmlFormatter());\n$logger->pushHandler($mailerHandler);\n$logger->addCritical('This is a critical message!');<\/pre>\nIn the example, I am using an HtmlFormatter object to the SwiftMailer and then define the $message and set content type to text\/html. In the email, this would look like this:<\/p>\n
![\"critical](\"https:\/\/stackify.com\/wp-content\/uploads\/2018\/07\/word-image-45.png\")
<\/p>\n
Most of the third-party handlers, formatters and processors can be found in the wiki<\/a>. You can always write your own if you want.! \ud83d\ude09<\/p>\n<\/a>Send your logs to Retrace<\/h3>\nLogs are crucial part in every application, it gives you information about your entire application and check whatever blindspot in your application. One of the advantage in using Retrace in your application is that it can support centralized logging. Centralized logging gives you the complete view of your environment. In manual PHP application, you go through the process of finding and guessing some of the errors and logs in your system.<\/p>\n
Below is an example of log monitoring work in Retrace<\/a>.<\/p>\n![\"image\"](\"https:\/\/stackify.com\/wp-content\/uploads\/2018\/07\/word-image-46.png\")
<\/p>\n
More information<\/h3>\n
See the following articles about PHP logging:<\/p>\n
\n- 18\u00a0PHP<\/em>\u00a0Tools for Developers of all Levels<\/a><\/li>\n
- Errors and Logs: Configure\u00a0PHP<\/em>\u00a0Applications<\/a><\/li>\n<\/ul>\n
<\/a>Summary<\/h3>\nMonolog is integrated into most of the popular frameworks like Laravel, Symfony, Slim, and many others, as of today, Monolog is one of the excellent tools available for logging libraries. I hope this article guides you, and helps you in logging your PHP applications.<\/p>\n
Retrace gives convenience in monitoring logs and troubleshoot problems quickly.<\/p>\n
Windows<\/h4>\ncomposer require monolog\/monolog<\/pre>\nIn case you are not using composer, download the PSR-3 source code<\/strong> and install to your application.<\/p>\nMake sure that you are using namespaces (to avoid a headache) so that you don\u2019t require a lot of files.<\/p>\n
<\/a>Create loggers<\/h3>\nFirst, when you create a logger, channel name should be included, so that you can distinguish your list of loggers.<\/p>\n
$logger = new MonologLogger('channel-name');\n$app->container->logger = $logger;<\/pre>\nIn the example above, \u2018channel-name\u2019 should be included in every log entry. This way you can easily look up and filter the entries; createanother channel for each component. Examples of these channels might include \u2018database\u2019, \u2018security\u2019, \u2019business\u2019, and others.<\/p>\n
Loggers by nature don\u2019t know how to handle logs, but we also have what are called handlers that can handle logs.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\n\n$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/app.log', Logger::DEBUG));\n$logger->info('This is a log! ^_^ ');\n$logger->warning('This is a log warning! ^_^ ');\n$logger->error('This is a log error! ^_^ ');\n\n<\/pre>\nIf you are using PHP 7.4 you will need to use this slightly modified code:<\/p>\n
require __DIR__ . '\/vendor\/autoload.php';<\/pre>\nuse Monolog\\Handler\\StreamHandler;<\/pre>\nuse Monolog\\Logger;<\/pre>\n$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(__DIR__ . '\/app.log', Logger::DEBUG));<\/pre>\nHandlers can be pushed as many as you need to a Logger instance. These types of handler will decide the kind of logs to be handled. In the example provided above, StreamHandler, reports entries in the file system app.log.<\/p>\n
<\/a>Intensity level<\/h3>\nAn intensity level is added to each log entry, along with channel name to allow you to check and filter the entries.<\/p>\n
As illustrated in RFC 5424<\/strong> which describes the syslog protocol, the following levels of intensity are applied in Monolog.<\/p>\n\n- DEBUG<\/strong>: Detailed debugging information.<\/li>\n
- INFO<\/strong>: Handles normal events. Example: SQL logs<\/li>\n
- NOTICE<\/strong>: Handles normal events, but with more important events<\/li>\n
- WARNING<\/strong>: Warning status, where you should take an action before it will become an error.<\/li>\n
- ERROR<\/strong>: Error status, where something is wrong and needs your immediate action<\/li>\n
- CRITICAL<\/strong>: Critical status. Example: System component is not available<\/li>\n
- ALERT<\/strong>: Immediate action should be exercised. This should trigger some alerts and wake you up during night time.<\/li>\n
- EMERGENCY<\/strong>: It is used when the system is unusable.<\/li>\n<\/ul>\n
An info log entry of a channel called \u2018channel-name\u2019, for example, looks like this:<\/p>\n
[2018-07-05 11:10:35] channel-name.INFO: This is a log entry!\n[2018-07-09 02:58:27] channel-name.WARNING: This is a log warning! ^_^ [] []\n[2018-07-09 02:58:27] channel-name.ERROR: This is a log error! ^_^ [] []<\/pre>\nMonolog stores one add for each type of intensity level, likely, error, notice, warning, info, and so on.<\/p>\n
<\/a>PHP example code<\/h3>\nThe following code is the basic sample setup to log to a file and to firephp on the Debug level.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerFirePHPHandler;\n\n$logger = new Logger('logger');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test_app.log', Logger::DEBUG));\n$logger->pushHandler(new FirePHPHandler());\n$logger->error('Logger is now Ready');<\/pre>\nIn the sample, it has two handlers in the stack to provide records in two different ways. FirePHPHandlers are described as it is joined on top of the stack. This permits you to tentatively append a logger with bubbling disabled, if you want to revoke other configured loggers.<\/p>\n
<\/a>Handler order<\/h3>\nWhen you add a log entry handler to the logger instance, it matters which order you push the handler. When a log entry is added, it will directly go to the handler stack. When a handler’s constructor is set to false, it stops traversing through the handler stack.<\/p>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerSwiftMailerHandler;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.example.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword('123456');\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['example-FROM@example.com' => 'Someone FROM']);\n$message->setTo(['someone-TO@example.com' => 'SomeoneTO']);\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushHandler(new SwiftMailerHandler($mailer, $message, Logger::CRITICAL, false));\n$logger->addCritical('Hey, a critical log entry!');<\/pre>\n<\/p>\n
First, you need to install SwiftMailer (composer require swiftmailer\/swiftmailer) to be able to use the SwiftMailerHandler. For you to be able to send emails, you need to use Swift_SmtpTransport, Swift_Message, and Swift_Mailer to join $mailer and $message to the SwiftMailerHandler instance.<\/p>\n
When you examine the last parameter of SwiftMailer’s constructor, it returns false for the last parameter, called $bubble parameter. Technically, by default, it returns true, but when set to false it means that it stops traversing the handler stack. This is a technique in which making the StreamHandler that is located at the bottom of the stack; it never store logs in the file system if SwiftMailerHandler manages the entry.<\/p>\n
<\/a>Array<\/h3>\nArray passing is as simple as the following code:<\/p>\n
$username = 'jmendez';\n$logger->addInfo('User registered', ['username' => $username]);<\/pre>\nThis is a way to pass an array to the add method such as addDebug, addInfo, etc.<\/p>\n
<\/a>Processors<\/h3>\nIn Monolog, you can create your own processor even though it provides a lot of processors by default. Processors are used to include information in log entries such as client’s IP and browser, and others. Here’s a sample code snippet:<\/p>\n
$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(function ($entry) {\n $entry['extra']['data'] = 'Hello world!';\n return $entry;\n});\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\nThe sample above would simply store the log entry in this format<\/p>\n
[2018-07-05 11:18:29] default.INFO: User registered {'username':'jmendez'} {\"data\":\"Hello world!\"}<\/pre>\nYou can also use the built-in processor that Monolog provides. You directly use the class and push an instance using the pushProcessor method. Here is sample code using pushProcessor.<\/p>\n
use MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologProcessorWebProcessor;\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(new WebProcessor());\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\n<\/a>Formatters<\/h3>\nIn Monolog, there are a lot of formatters that can be used. You can find some built-in formatters here<\/a>. You can also customize the format of the logs that are written in files, emails, databases, and other handlers.<\/p>\n$record['formatted']<\/pre>\nis the most common way to use a handler with a value to be directly put into the log device. Formatters can be customized, so you can write your own. Here is a simple configuration for a built-in formatter class that formats the log sent by email, which can be understandable by everyone who will be using your system.<\/p>\n
use MonologLogger;\nuse MonologHandlerSwiftMailerHandler;\nuse MonologFormatterHtmlFormatter;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.gmail.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword(123456);\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['fromuser@example.com' => 'From User']);\n$message->setTo(['touser@example.com' => 'To User']);\n$message->setContentType(\"text\/html\");\n\n$logger = new Logger('default');\n$mailerHandler = new SwiftMailerHandler($mailer, $message, Logger::CRITICAL);\n$mailerHandler->setFormatter(new HtmlFormatter());\n$logger->pushHandler($mailerHandler);\n$logger->addCritical('This is a critical message!');<\/pre>\nIn the example, I am using an HtmlFormatter object to the SwiftMailer and then define the $message and set content type to text\/html. In the email, this would look like this:<\/p>\n
<\/p>\n
Most of the third-party handlers, formatters and processors can be found in the wiki<\/a>. You can always write your own if you want.! \ud83d\ude09<\/p>\n<\/a>Send your logs to Retrace<\/h3>\nLogs are crucial part in every application, it gives you information about your entire application and check whatever blindspot in your application. One of the advantage in using Retrace in your application is that it can support centralized logging. Centralized logging gives you the complete view of your environment. In manual PHP application, you go through the process of finding and guessing some of the errors and logs in your system.<\/p>\n
Below is an example of log monitoring work in Retrace<\/a>.<\/p>\n<\/p>\n
More information<\/h3>\n
See the following articles about PHP logging:<\/p>\n
\n- 18\u00a0PHP<\/em>\u00a0Tools for Developers of all Levels<\/a><\/li>\n
- Errors and Logs: Configure\u00a0PHP<\/em>\u00a0Applications<\/a><\/li>\n<\/ul>\n
<\/a>Summary<\/h3>\nMonolog is integrated into most of the popular frameworks like Laravel, Symfony, Slim, and many others, as of today, Monolog is one of the excellent tools available for logging libraries. I hope this article guides you, and helps you in logging your PHP applications.<\/p>\n
Retrace gives convenience in monitoring logs and troubleshoot problems quickly.<\/p>\n
In case you are not using composer, download the PSR-3 source code<\/strong> and install to your application.<\/p>\n Make sure that you are using namespaces (to avoid a headache) so that you don\u2019t require a lot of files.<\/p>\n First, when you create a logger, channel name should be included, so that you can distinguish your list of loggers.<\/p>\n In the example above, \u2018channel-name\u2019 should be included in every log entry. This way you can easily look up and filter the entries; createanother channel for each component. Examples of these channels might include \u2018database\u2019, \u2018security\u2019, \u2019business\u2019, and others.<\/p>\n Loggers by nature don\u2019t know how to handle logs, but we also have what are called handlers that can handle logs.<\/p>\n If you are using PHP 7.4 you will need to use this slightly modified code:<\/p>\n Handlers can be pushed as many as you need to a Logger instance. These types of handler will decide the kind of logs to be handled. In the example provided above, StreamHandler, reports entries in the file system app.log.<\/p>\n An intensity level is added to each log entry, along with channel name to allow you to check and filter the entries.<\/p>\n As illustrated in RFC 5424<\/strong> which describes the syslog protocol, the following levels of intensity are applied in Monolog.<\/p>\n An info log entry of a channel called \u2018channel-name\u2019, for example, looks like this:<\/p>\n Monolog stores one add for each type of intensity level, likely, error, notice, warning, info, and so on.<\/p>\n The following code is the basic sample setup to log to a file and to firephp on the Debug level.<\/p>\n In the sample, it has two handlers in the stack to provide records in two different ways. FirePHPHandlers are described as it is joined on top of the stack. This permits you to tentatively append a logger with bubbling disabled, if you want to revoke other configured loggers.<\/p>\n When you add a log entry handler to the logger instance, it matters which order you push the handler. When a log entry is added, it will directly go to the handler stack. When a handler’s constructor is set to false, it stops traversing through the handler stack.<\/p>\n First, you need to install SwiftMailer (composer require swiftmailer\/swiftmailer) to be able to use the SwiftMailerHandler. For you to be able to send emails, you need to use Swift_SmtpTransport, Swift_Message, and Swift_Mailer to join $mailer and $message to the SwiftMailerHandler instance.<\/p>\n When you examine the last parameter of SwiftMailer’s constructor, it returns false for the last parameter, called $bubble parameter. Technically, by default, it returns true, but when set to false it means that it stops traversing the handler stack. This is a technique in which making the StreamHandler that is located at the bottom of the stack; it never store logs in the file system if SwiftMailerHandler manages the entry.<\/p>\n Array passing is as simple as the following code:<\/p>\n This is a way to pass an array to the add method such as addDebug, addInfo, etc.<\/p>\n In Monolog, you can create your own processor even though it provides a lot of processors by default. Processors are used to include information in log entries such as client’s IP and browser, and others. Here’s a sample code snippet:<\/p>\n The sample above would simply store the log entry in this format<\/p>\n You can also use the built-in processor that Monolog provides. You directly use the class and push an instance using the pushProcessor method. Here is sample code using pushProcessor.<\/p>\n In Monolog, there are a lot of formatters that can be used. You can find some built-in formatters here<\/a>. You can also customize the format of the logs that are written in files, emails, databases, and other handlers.<\/p>\n is the most common way to use a handler with a value to be directly put into the log device. Formatters can be customized, so you can write your own. Here is a simple configuration for a built-in formatter class that formats the log sent by email, which can be understandable by everyone who will be using your system.<\/p>\n In the example, I am using an HtmlFormatter object to the SwiftMailer and then define the $message and set content type to text\/html. In the email, this would look like this:<\/p>\n Most of the third-party handlers, formatters and processors can be found in the wiki<\/a>. You can always write your own if you want.! \ud83d\ude09<\/p>\n Logs are crucial part in every application, it gives you information about your entire application and check whatever blindspot in your application. One of the advantage in using Retrace in your application is that it can support centralized logging. Centralized logging gives you the complete view of your environment. In manual PHP application, you go through the process of finding and guessing some of the errors and logs in your system.<\/p>\n Below is an example of log monitoring work in Retrace<\/a>.<\/p>\n See the following articles about PHP logging:<\/p>\n Monolog is integrated into most of the popular frameworks like Laravel, Symfony, Slim, and many others, as of today, Monolog is one of the excellent tools available for logging libraries. I hope this article guides you, and helps you in logging your PHP applications.<\/p>\n Retrace gives convenience in monitoring logs and troubleshoot problems quickly.<\/p>\n<\/a>Create loggers<\/h3>\n
$logger = new MonologLogger('channel-name');\n$app->container->logger = $logger;<\/pre>\nrequire_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\n\n$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/app.log', Logger::DEBUG));\n$logger->info('This is a log! ^_^ ');\n$logger->warning('This is a log warning! ^_^ ');\n$logger->error('This is a log error! ^_^ ');\n\n<\/pre>\nrequire __DIR__ . '\/vendor\/autoload.php';<\/pre>\n
use Monolog\\Handler\\StreamHandler;<\/pre>\n
use Monolog\\Logger;<\/pre>\n
$logger = new Logger('channel-name');\n$logger->pushHandler(new StreamHandler(__DIR__ . '\/app.log', Logger::DEBUG));<\/pre>\n<\/a>Intensity level<\/h3>\n
\n
[2018-07-05 11:10:35] channel-name.INFO: This is a log entry!\n[2018-07-09 02:58:27] channel-name.WARNING: This is a log warning! ^_^ [] []\n[2018-07-09 02:58:27] channel-name.ERROR: This is a log error! ^_^ [] []<\/pre>\n
<\/a>PHP example code<\/h3>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerFirePHPHandler;\n\n$logger = new Logger('logger');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test_app.log', Logger::DEBUG));\n$logger->pushHandler(new FirePHPHandler());\n$logger->error('Logger is now Ready');<\/pre>\n<\/a>Handler order<\/h3>\n
require_once(DIR.'\/vendor\/autoload.php');\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologHandlerSwiftMailerHandler;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.example.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword('123456');\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['example-FROM@example.com' => 'Someone FROM']);\n$message->setTo(['someone-TO@example.com' => 'SomeoneTO']);\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushHandler(new SwiftMailerHandler($mailer, $message, Logger::CRITICAL, false));\n$logger->addCritical('Hey, a critical log entry!');<\/pre>\n<\/p>\n<\/a>Array<\/h3>\n
$username = 'jmendez';\n$logger->addInfo('User registered', ['username' => $username]);<\/pre>\n<\/a>Processors<\/h3>\n
$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(function ($entry) {\n $entry['extra']['data'] = 'Hello world!';\n return $entry;\n});\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\n[2018-07-05 11:18:29] default.INFO: User registered {'username':'jmendez'} {\"data\":\"Hello world!\"}<\/pre>\nuse MonologLogger;\nuse MonologHandlerStreamHandler;\nuse MonologProcessorWebProcessor;\n\n$logger = new Logger('default');\n$logger->pushHandler(new StreamHandler(DIR<\/strong>.'\/test.log', Logger::INFO));\n$logger->pushProcessor(new WebProcessor());\n$logger->addInfo('User registered', ['username'=>'jmendez']);<\/pre>\n<\/a>Formatters<\/h3>\n
$record['formatted']<\/pre>\n
use MonologLogger;\nuse MonologHandlerSwiftMailerHandler;\nuse MonologFormatterHtmlFormatter;\n\n\/\/ Create the Transport\n$transporter = new Swift_SmtpTransport('smtp.gmail.com', 465, 'ssl');\n$transporter->setUsername('user@example.com');\n$transporter->setPassword(123456);\n\n\/\/ Create the Mailer using your created Transport\n$mailer = new Swift_Mailer($transporter);\n\n\/\/ Create a message\n$message = (new Swift_Message('A CRITICAL log was added'));\n$message->setFrom(['fromuser@example.com' => 'From User']);\n$message->setTo(['touser@example.com' => 'To User']);\n$message->setContentType(\"text\/html\");\n\n$logger = new Logger('default');\n$mailerHandler = new SwiftMailerHandler($mailer, $message, Logger::CRITICAL);\n$mailerHandler->setFormatter(new HtmlFormatter());\n$logger->pushHandler($mailerHandler);\n$logger->addCritical('This is a critical message!');<\/pre>\n<\/p>\n<\/a>Send your logs to Retrace<\/h3>\n
<\/p>\nMore information<\/h3>\n
\n
<\/a>Summary<\/h3>\n