We have quite a large deployment of DCRUM at a client. One of their big applications is internet facing and generates a lot of raw CAS sessions Capture.PNG
Our threshold is 6M and can't be changed, what is restricting us from doing so?
What exactly happens when we hit that threshold? What are we losing when threshold is breached? Data is not put into the cache but put into the DB?
Given our scenario where we're capturing well over 50M sessions a day, how can we best monitor this app?
It's not the same as server/client cache threshold that protect the DB from being overloaded and reaching/exceeding 6M of sessions if wouldn't be a problem if the memory consumption and data files processing time by CAS is OK, if the DB size is acceptable...
As long as the CAS(es) are coping with the load, we can increase that threshold so it's not alerting the customer. I'll check this when on site next.
I'd expect teh session count to be much higher than usual, due primarily in part to the 1 minute intervals (having 5 times the resolution).