The ability to add custom QoE monitoring for non-HTTP applications.
Hi,
I am not able to locate nodes for deploying sensors.
Can someone help to check?
Best Regards,
nodes for sensors must be monitored by orion before you can deploy to them.
How do you want to define such application?
For HTTPS in same way as HTTP?
Target port or host:port?
Are you missing some public service or common application that can be added in future?
We would like to define the application by the target of the traffic. For instance all traffic going to this IP:Port or even better a URL:Port is for Application X.
This would be for industry specific, not common, applications. For example traffic going to a cloud operator who is offering a service.
I really agree with this. Our company has multiple in-house developed applications running on multiple servers through load balancers, using custom, high port numbers (tcp/65003), or even better, being able to specify IP addresses (or ranges of IP addresses, and ports, for instance "to or from 192.168.150.230:65006" or "to or from 192.168.220.0/29:65120"
For instance, a virtual service going through a load balancer, behind which, we might have 6 "real" servers, ip addresses 192.168.220.1 - 192.168.220.6, each running multiple applications on different ports, like tcp/65120, tcp/65121, etc, and we'd like to be able to monitor QoE on all those specific ports for each server.
Thanks!
Mark
Will this include for Could Applications?
Yatin
Hey,
Just wondering how this is tracking along.
My guess is that it's not going to happen, since this would cut into the market for the SAM (Server Application Management.) Of course, I'm just assuming that SAM can integrate with QOE.
In the mean time, I was going to give Nagios another try, but I recall all the hassles of the configuration files and the fact that I'm not a perl programmer. I learned about a different system that puts a friendlier, graphical face on Nagios, plus a number of additional features, and so far I like it, Check_MK.
I would recommend that QoE have support for protocols used for real time traffic like VOIP and IP Video. These are extremely common applications that are very sensitive to network quality issues.
It's been forever, I feel this could use a bump. #bumpsquad . I wonder if this will ever be considered considering a lot of the world is now mostly HTTPS?
BUMP.
Not much choice in what to monitor for us - I already have monitors for http. We should be able to create custom QOE apps - like, Syslog, or other applications.
BUMP
HTTPS custom apps would be much more valuable than HTTP apps this day and age.
BUMP! also the ability to monitor not just the https but the custom application as well.
I guess that the problem to monitor HTTPS applications is that these packets will be encrypted (SSL), therefore it is not possible to access the URL within the HTTPS packet.
The solution that other vendors (security tools) are using is to monitor DNS traffic as well, and correlate DNS request with IP address on the HTTPS. This is if i do a DNS lookup on www.google.com and IP address resolved is x.x.x.x, if later on I found traffic using HTTPS on the IP address x.x.x.x I can imagine that is HTTPS traffic towards www.google.com.
Not sure if SolarWinds is able to do something similar.
TTT
Would like to write custom QOE apps!
are https apps in the pipeline do we know? this is a really old request yet seems like its the only feature worth having for QoE, not being able to monitor https traffic (even to just do domain based recognition would be a lot of help) makes the module near useless
major BUMP! how is this not a thing yet?!
Most of our business related applications are non-http. This is a must and mandator my for using this feature
