Rando QoE Sensors

Question

Hey folks -

Anyone else seeing situations where server-based QoE sensors are seeing random application sensors get detected (and added) on servers with small amounts of data?

Things like HiveStor, Gnutella, Shoutcast, etc?

We have these QoE apps being detected/added, but they obviously are not present, and there is maybe ONE detected instance, with very little data being recorded.

What gives? At this point, I have to turn off auto-detection on 80% of the applications due to false positives.

Thoughts?

Running: Orion Platform 2019.2 HF1, WPM 3.0.0, SRM 6.9.0, NPM 12.5, VMAN 8.5.0 HF1, SAM 6.9.1, NetPath 1.1.5

jcordle · Answer

I've removed them all manually so far. Let me see if I can get a few back.

Did not know about the global "at least" setting. I probably should've used that first.

Also - the QoE sensor page has the column headings displayed strange. They are not over the top of their respective columns. I can reproduce this in FireFox and Chrome. (see attached screenshot)

jason.carrier · Answer

Thanks for the feedback!

Have you already checked out the "Global QoE Settings" page? I'm thinking if you change the "Applications that have at least XX % of total QoE trafffic" setting to something like 5%, it will solve the errant messages from the false positives and let you keep auto-detection turned on.

This doesn't explain why the false positives are happening in the first place though. Would you mind sharing some screenshots? Be happy to look into this issue a bit further.

jcordle · Answer

Also, jason.carrier​, as a matter of product feedback, there should be some sort of global QoE sensor detection variables...

Right now we only have "auto detection on or off", so I end up having to turn off 80% of the apps after they've been "detected", when there's no real reason to have them there,  and I'd really like to see things like "add sensor if: detected X times over Y time period" or "add sensor if: X amount of data over Y time period".

Thanks,

JC