Add monitoring for PubSub commands in Redis
The primary purpose of Redis in my architecture is for its Publish/Subscribe functionality. I'd like if Redsmin let me monitor the data being passed through my PubSub channels.
Vote 539
shared this idea
-
AdminBruce
(Founder, Redsmin)
commented
>This wildcard accounts for the bulk of the traffic through Redis. I have a few other small channels as well.
It's definitely easy for the direct server to create a second channel for psubscribing on demand.> Most of the messages that get published are JSON strings.
Good news, no need for us to implement a reader for each message format> Being able to see a "live stream" of the messages coming through the channel would be cool,
It would be cool yes, but if you publish 10 000msg/s, Redsmin won't be able to display them in the UI and thus a backpressure must be set up> as would continuous monitoring of the size and volume of the messages.
We are currently rewriting from scratch our monitoring service and then we will work on a new alerting service. I forward to our team your request on that matter.> Persistence of the actual messages would be cool option, but that might be more demanding on the Redsmin servers.
Indeed that would be outside Redsmin feature-set :) -
Vote 539
commented
Hello! My application uses the PSUBSCRIBE command to listen on a channel wildcard. This wildcard accounts for the bulk of the traffic through Redis. I have a few other small channels as well.
Most of the messages that get published are JSON strings.
Being able to see a "live stream" of the messages coming through the channel would be cool, as would continuous monitoring of the size and volume of the messages. Persistence of the actual messages would be cool option, but that might be more demanding on the Redsmin servers.
Thanks!