$processors
$processors : array<mixed,callable>
Handler sending logs to Zend Monitor
Classes extending it should (in most cases) only implement write($record)
setFormatter(\Monolog\Formatter\FormatterInterface $formatter)
{@inheritdoc}
| \Monolog\Formatter\FormatterInterface | $formatter |
__construct(string|integer $level = \Monolog\Logger::DEBUG, boolean $bubble = true)
| string|integer | $level | The minimum logging level at which this handler will be triggered. |
| boolean | $bubble | Whether the messages that are handled can bubble up the stack or not. |
close()
Closes the handler.
Ends a log cycle and frees all resources used by the handler.
Closing a Handler means flushing all buffers and freeing any open resources/handles.
Implementations have to be idempotent (i.e. it should be possible to call close several times without breakage) and ideally handlers should be able to reopen themselves on handle() after they have been closed.
This is useful at the end of a request and will be called automatically when the object is destroyed if you extend Monolog\Handler\Handler.
If you are thinking of calling this method yourself, most likely you should be calling ResettableInterface::reset instead. Have a look.
writeZendMonitorCustomEvent(string $type, string $message, array $formatted, integer $severity)
Write to Zend Monitor Events
| string | $type | Text displayed in "Class Name (custom)" field |
| string | $message | Text displayed in "Error String" |
| array | $formatted | Displayed in Custom Variables tab |
| integer | $severity | Set the event severity level (-1,0,1) |