[GH-ISSUE #34] Calculating a hash identifying the message #9

Closed
opened 2026-03-04 02:11:17 +03:00 by kerem · 4 comments
Owner

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.

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.
kerem 2026-03-04 02:11:17 +03:00
  • closed this issue
  • added the
    Feature
    label
Author
Owner

@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.

<!-- gh-comment-id:1500174 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:1500190 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:1500349 --> @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.
Author
Owner

@Seldaek commented on GitHub (May 26, 2016):

This is kinda fixed by https://github.com/Seldaek/monolog/blob/master/src/Monolog/Handler/DeduplicationHandler.php

<!-- gh-comment-id:221979013 --> @Seldaek commented on GitHub (May 26, 2016): This is kinda fixed by https://github.com/Seldaek/monolog/blob/master/src/Monolog/Handler/DeduplicationHandler.php
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#9
No description provided.