According to document, the sticky session is required for the communication between Dynatrace Managed Cluster and Mission Control.
but the proxy must allow web sockets and, if the proxy is clustered, it must provide sticky sessions for web socket communication.
Could you tell us why the proxy must provide the sticky session for web socket communication if the proxy is clustered?
Solved! Go to Solution.
Below information taken from the internet where sticky session for web socket communications explained.
I'm not sure that the documentation is up-to-date here. Dynatrace uses a nginx to manage sticky sessions.
https://www.dynatrace.com/news/blog/session-sticki... (this feature has been GA since 138)
I checked the article. But it seems that the article says the connection between Web UI and Dynatrace Managed Cluster.
My question is about the communication between Dynatrace Managed Cluster and Mission Control.
Or, it is needed the same requirement for the communication of Web UI and Mission Control?