mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 16:15:49 +03:00
[GH-ISSUE #34] Calculating a hash identifying the message #9
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stof on GitHub (May 31, 2011).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/34
Monolog should be able to calculate a hash identifying a message. This would allows storing them in a storage when an error occur and flushing them in an handler only once instea dof having one message per request.
@Seldaek commented on GitHub (Jul 4, 2011):
This should use the IntrospectionProcessor code and crc32 the output. The message and others can't be taken into consideration because they could be input or date-sensitive.
@stof commented on GitHub (Jul 4, 2011):
There is issue with this. Think for instance to the Symfony2 ExceptionListener. All exceptions are logged at the same line, so this will not be enough to determine if this is the same mesage.
@Seldaek commented on GitHub (Jul 4, 2011):
Well, we could have another hash computation for Symfony2 that ignores the exception listener or something. But yeah I agree this could be problematic. It can wait until 1.1 anyway.
@Seldaek commented on GitHub (May 26, 2016):
This is kinda fixed by https://github.com/Seldaek/monolog/blob/master/src/Monolog/Handler/DeduplicationHandler.php