Releases: Seldaek/monolog
Releases · Seldaek/monolog
1.26.1
2.2.0
- Added JSON_PARTIAL_OUTPUT_ON_ERROR to default json encoding flags, to avoid dropping entire context data or even records due to an invalid subset of it somewhere
- Added setDateFormat to NormalizerFormatter (and Line/Json formatters by extension) to allow changing this after object creation
- Added RedisPubSubHandler to log records to a Redis channel using PUBLISH
- Added support for Elastica 7, and deprecated the $type argument of ElasticaFormatter which is not in use anymore as of Elastica 7
- Added support for millisecond write timeouts in SocketHandler, you can now pass floats to setWritingTimeout, e.g. 0.2 is 200ms
- Added support for unix sockets in SyslogUdpHandler (set $port to 0 to make the $host a unix socket)
- Added handleBatch support for TelegramBotHandler
- Added RFC5424e extended date format including milliseconds to SyslogUdpHandler
- Added support for configuring handlers with numeric level values in strings (coming from e.g. env vars)
- Fixed Wildfire/FirePHP/ChromePHP handling of unicode characters
- Fixed PHP 8 issues in SyslogUdpHandler
- Fixed internal type error when mbstring is missing
1.26.0
2.1.1
- Fixed removing of json encoding options
- Fixed type hint of $level not accepting strings in SendGridHandler and OverflowHandler
- Fixed SwiftMailerHandler not accepting email templates with an empty subject
- Fixed array access on null in RavenHandler
- Fixed unique_id in WebProcessor not being disableable
1.25.5
2.1.0
- Added
JSON_INVALID_UTF8_SUBSTITUTE
to default json flags, so that invalid UTF8 characters now get converted to � instead of being converted from ISO-8859-15 to UTF8 as it was before, which was hardly a comprehensive solution - Added
$ignoreEmptyContextAndExtra
option to JsonFormatter to skip empty context/extra entirely from the output - Added
$parseMode
,$disableWebPagePreview
and$disableNotification
options to TelegramBotHandler - Added tentative support for PHP 8
- NormalizerFormatter::addJsonEncodeOption and removeJsonEncodeOption are now public to allow modifying default json flags
- Fixed GitProcessor type error when there is no git repo present
- Fixed normalization of SoapFault objects containing deeply nested objects as "detail"
- Fixed support for relative paths in RotatingFileHandler
1.25.4
2.0.2
- Fixed ElasticsearchHandler swallowing exceptions details when failing to index log records
- Fixed normalization of SoapFault objects containing non-strings as "detail" in LineFormatter
- Fixed formatting of resources in JsonFormatter
- Fixed RedisHandler failing to use MULTI properly when passed a proxied Redis instance (e.g. in Symfony with lazy services)
- Fixed FilterHandler triggering a notice when handleBatch was filtering all records passed to it
- Fixed Turkish locale messing up the conversion of level names to their constant values
1.25.3
- Fixed formatting of resources in JsonFormatter
- Fixed RedisHandler failing to use MULTI properly when passed a proxied Redis instance (e.g. in Symfony with lazy services)
- Fixed FilterHandler triggering a notice when handleBatch was filtering all records passed to it
- Fixed Turkish locale messing up the conversion of level names to their constant values
2.0.1
- Fixed normalization of Traversables to avoid traversing them as not all of them are rewindable
- Fixed setFormatter/getFormatter to forward to the nested handler in FilterHandler, FingersCrossedHandler, BufferHandler, OverflowHandler and SamplingHandler
- Fixed BrowserConsoleHandler formatting when using multiple styles
- Fixed normalization of exception codes to be always integers even for PDOException which have them as numeric strings
- Fixed normalization of SoapFault objects containing non-strings as "detail"
- Fixed json encoding across all handlers to always attempt recovery of non-UTF-8 strings instead of failing the whole encoding
- Fixed ChromePHPHandler to avoid sending more data than latest Chrome versions allow in headers (4KB down from 256KB).
- Fixed type error in BrowserConsoleHandler when the context array of log records was not associative.