How can I tell if my SignalR (Redis) panel really works as it should?

Question

I am currently playing SignalR 2.0.3, scaling it with BackPlane, which uses Redis for windows http://msopentech.com/blog/2013/04/22/redis-on-windows-stable-and-reliable/

I integrated with the corresponding SignalR.Redis package in VS.

I made the following changes to my launch:

GlobalHost.DependencyResolver.UseRedis( server: "localhost", port: 6379, password: string.Empty, eventKey: "BroadcasterExample" ); app.MapSignalR(hubConfiguration); 

He builds great. My client seems to be connecting to OK. I can send notifications between client and server and vice versa.

From the Redis client, I can enter:

 get BroadcasterExample which returns: "3" 

I assume that everything works, but ...

A couple of questions: 1) How can I say that this really works?

2) What can I check on the Redis server (although the Redis client)?

3) What is stored in data structures (key / value pairs, lists, hashes, sets)?

I would like to have a more detailed idea of ​​what is happening. I looked at the commands: http://redis.io/commands Nothing jumps at me, which will help me outline what is actually happening.

Can someone point me in the right direction here?

Thanks Johnb

Answer 1

1) I believe that you have already checked that it works when you run "get BroadcasterExample" and it returned "3". BroadcasterExample is the name of the channel through which SignalR will send messages, and I think 3 represents the number of messages processed. When you send more messages using SignalR, you should see this number.

2) A good way to say that everything works is to subscribe to the BroadcasterExample channel using the redis client and see how the messages go. From the client, run:

 subscribe BroadcasterExample 

3) SignalR will probably just save this key, the "BroadcasterExample" key. SignalR really just uses the Redis publish / subscribe function without storing any data.

Answer 2

The answer from jaggedaz has useful information. I would also add that you can run another test quickly enough by placing your application twice, on two different ports, using IIS Express. If you then connect 2 browser windows to these two different instances and start exchanging messages (for example, broadcast messages with everyone), you will see that they pass through both clients, which is possible only during normal operation of the backplane.