Add anti-404 activation strategy service/class about monolog-bundle HOT 9 CLOSED

Excluding this works for me - ^/

from monolog-bundle.

I do exclude certain 404's where I know the cause, but not generally all 404s.

Maybe a cookbook entry would be better to allow people to adjust it to their needs.

from monolog-bundle.

Well how do you typically do this? In general all I see in 404s are a bunch of hacking attempts from scanners trying to exploit phpmyadmin leaks and similar.. I don't know if it's possible to exclude all of those, but I usually just increase the level to CRITICAL just to get rid of the 404s, so I wouldn't mind this "dumb" exclusion mode, it would still be an improvement.

from monolog-bundle.

@Seldaek does the ActivationStrategy of the FingersCrossedHandler could fit your needs for this or do you expect another feature ? If it is enough, it is simply a documentation issue then.

from monolog-bundle.

@stof yes I'm talking about the ActivationStrategy, but no I don't think it's just documentation, providing one configured by default means people get those benefits by default and then can more easily tweak it since it'd just be changing the class of the service or pointing to another service. That's just my point of view anyway.

from monolog-bundle.

👍 for not filling the logs with 404's - or at least providing an easy way to stop it.

from monolog-bundle.

OK this is now possible as:

monolog:
    handlers:
        main:
            type:         fingers_crossed
            action_level: error
            handler:      nested
            excluded_404s:
                - ^/foo/

from monolog-bundle.

Is there a way to make it just exclude all 404s, not just for a specific url? I can't get this to work.

from monolog-bundle.

I tried that, and it didn't work, so must have been something else wrong. I thought that would do it so I just wanted to check. Thanks :)

from monolog-bundle.