This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

QoE for Custom HTTPS App

I had expected to be able to add our two custom HTTPS applications to QoE given they use non-standard ports and specific internal IPs. It looks like only HTTP can be added via the console. Is there a way to build a filter based on server IP range and port? Has anyone else run in to a similar issue and found a workaround?

  • You probably have already know this, but QoE can automatically search for endpoints and ports after you deploy the sensor(s) and is turned on by default.  Try deploying it if you haven't already, and see if it picks up those ports and IP's automatically. 

  • Opened a support ticket for this issue. Custom HTTPS applications cannot be added at this time. Since QOE is not just IP/Port based, but more inteligent, it does not pick up our custom internal application.

    I submitted a feature request, so hopefully this will come out in a future release.