Replies: 1 comment
-
RedisInsight, PgWeb, PgAdmin etc etc are only used in local dev. They are excluded in publish mode.
Crank up the log level on the signalr logs. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm struggling a bit with Redis + SingalR, I'm hoping to get some pointers.
Issue 1: RedisInsight not deployed
I'm declaring my redis cache in aspire via:
I see that container when running locally, but I don't see any additional container created for Redis Insight when provisioned to Azure. I can't see anything specifically created for it when I run 'azd infra synth', should I?
Issue 2: Odd issue's with SignalR set to use the redis cache as a backplane for scale out.
I've got a chat client using signalR, but I'm finding when deployed, I'm not getting group broadcast messages back. The connection looks fine in the browser and I can see it sending messages, but no responses coming back, usually just after deployment (which includes deploying both cache and the app).
SignalR is configured to use Redis:
The app with the signalR hub has sticky sessions enabled on ingress.
If I restart the cache container, it will start working again, so seems certainly related. I don't see any console errors, anything in the Aspire Dashboard (which is why I wanted RedisInsight, to see if there where any clues there). I can certainly look to Azure SignalR service, but I'd like to understand what's going on with the current setup, where this behavior comes from and how to get more information out of it.
Beta Was this translation helpful? Give feedback.
All reactions