Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating multiple gelf handlers sends all messages to only one #62

Closed
alex88 opened this issue Nov 22, 2013 · 2 comments
Closed

Creating multiple gelf handlers sends all messages to only one #62

alex88 opened this issue Nov 22, 2013 · 2 comments

Comments

@alex88
Copy link

alex88 commented Nov 22, 2013

I've creating the following configuration:

monolog:
    handlers:
        main:
            type:           fingers_crossed
            action_level:   critical
            handler:        nested
        nested:
            type:           stream
            path:           "%kernel.logs_dir%/%kernel.environment%.log"
            level:          debug
        info:
            type:           stream
            path:           "%kernel.logs_dir%/%kernel.environment%.log"
            level:          info
        graylog2:
            type:           gelf
            level:          info
            publisher:
                hostname:   %logging_host%
                port:       12201
        graylog2_ita:
            type:           gelf
            level:          info
            publisher:
                hostname:   151.x.x.x
                port:       12201
        console:
            type:           console

The problem is that both messages for graylog2 and graylog2_ita are sent to the last one (duplicated).

I've tried to use also a key "name" inside the handlers and the groupHandler but still they're sent to only one of the servers.

@Seldaek
Copy link
Member

Seldaek commented Nov 23, 2013

Try again with latest dev-master, but it should be good now

@alex88
Copy link
Author

alex88 commented Nov 25, 2013

Works like a charm! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants