[GH-ISSUE #281] websocket Handler #92

New issue

Closed

opened 2026-03-04 02:12:06 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 02:12:06 +03:00

Owner

Originally created by @wojons on GitHub (Dec 5, 2013).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/281

Would be cool to get a web socket handler in place. better then sending an http request all the time. But still lets you have headers if you need to auth something or pass some extra meta data around, thats the same for each message.

Originally created by @wojons on GitHub (Dec 5, 2013). Original GitHub issue: https://github.com/Seldaek/monolog/issues/281 Would be cool to get a web socket handler in place. better then sending an http request all the time. But still lets you have headers if you need to auth something or pass some extra meta data around, thats the same for each message.

kerem closed this issue

2026-03-04 02:12:07 +03:00

kerem commented

2026-03-04 02:12:08 +03:00

Author

Owner

@Seldaek commented on GitHub (Dec 6, 2013):

I don't quite see the point of web sockets with regard to logging. Where from/to do you want to log things?

@Seldaek commented on GitHub (Dec 6, 2013): I don't quite see the point of web sockets with regard to logging. Where from/to do you want to log things?

kerem commented

2026-03-04 02:12:08 +03:00

Author

Owner

@wojons commented on GitHub (Dec 6, 2013):

I know I could use sockets and do it like that but for examples with websockets allows for nginx load balancing and can handle in coming logs with things like tornado for python. It makes building a logging service or platform really easy. Since there are headers with for different customers api keys blah blah blah

@wojons commented on GitHub (Dec 6, 2013): I know I could use sockets and do it like that but for examples with websockets allows for nginx load balancing and can handle in coming logs with things like tornado for python. It makes building a logging service or platform really easy. Since there are headers with for different customers api keys blah blah blah

kerem commented

2026-03-04 02:12:08 +03:00

Author

Owner

@Seldaek commented on GitHub (Dec 6, 2013):

I'm still not sure what you want. A monolog handler that posts to a
websocket-capable server? If yes ok, but then it should be built for a
specific websocket implementation since websockets are just sockets over
http.. You still need a logging protocol behind. So if you have a use case
then you could write a handler for this, but in general asking for
websocket support is too vague I think.

@Seldaek commented on GitHub (Dec 6, 2013): I'm still not sure what you want. A monolog handler that posts to a websocket-capable server? If yes ok, but then it should be built for a specific websocket implementation since websockets are just sockets over http.. You still need a logging protocol behind. So if you have a use case then you could write a handler for this, but in general asking for websocket support is too vague I think.

kerem commented

2026-03-04 02:12:08 +03:00

Author

Owner

@wojons commented on GitHub (Dec 6, 2013):

@Seldaek i totally see where your comming from. I was hoping to leave it open enough that other devs that wanna log to web sockets can easily. In default it would json format for the log data that is sent and then termante by \n or something pretty easy and straight forward. I feel like there are a few websocket protocols right now but this seems to be the RFC for it http://tools.ietf.org/html/rfc6455

@wojons commented on GitHub (Dec 6, 2013): @Seldaek i totally see where your comming from. I was hoping to leave it open enough that other devs that wanna log to web sockets can easily. In default it would json format for the log data that is sent and then termante by \n or something pretty easy and straight forward. I feel like there are a few websocket protocols right now but this seems to be the RFC for it http://tools.ietf.org/html/rfc6455

kerem commented

2026-03-04 02:12:08 +03:00

Author

Owner

@Seldaek commented on GitHub (Mar 23, 2014):

Closing until there is some code to talk about, because I don't get it as it is.

@Seldaek commented on GitHub (Mar 23, 2014): Closing until there is some code to talk about, because I don't get it as it is.

kerem referenced this issue

2026-03-04 03:02:52 +03:00

[PR #92] [CLOSED] fix for issue #91 #927