1 person found this helpful
Telemetry in the flash player only supports connecting to one TCP/IP address at a time. Scout can listen to any number of connections from different flash players - on other machines or other browsers, but the core flash player in each browser can only have one active telemetry session. You could probably write a proxy to listen to the telemetry session and forward it to multiple instances of Scout but I've never tried that. Of course you can also save a session and view it in multiple instances of Scout.
I realize this is an old thread, but I couldn't help but consider this interesting question.
You could, on a linux or OS X box -- as along as they have the netcat and tee utilities -- listen on the telemetry port and forward to multiple recipients. The command to listen to port 7934 and relay to both two other machines, 10.0.1.100:7934 and 10.0.1.101:7934, is:
nc -l 0.0.0.0 7934 | tee >(nc 10.0.1.100 7934) >(nc 10.0.1.101 7934) > /dev/null
You can add as many recipients as you like with more >(nc ipaddress 7934) clauses in the middle.
In this case, point your .telemetry.cfg at the machine running this script, and it will forward the telemetry data to the IP addresses you specify. If they're all running Scout, they should all see the data.
For kicks, here's a couple other useful commands:
Capture telemetry data to a file: nc -l 0.0.0.0 7934 > data.flm
Push saved data.flm file to Scout on localhost port 7934: nc localhost 7934 < data.flm
Just one more reason Linux rules. Hope this helps someone!