See the package readme for instructions for enabling this HTTProvider.
Richard
Yes it is a great data source… even better with this php script to clarify the data:
I push our drupal programmer here to get me some code to:
extract the ip’s from serverInfoXML to build an automatic web page to get the addresses of the origins and all edges, and for each servers bring a JW player window play the streams…
all of this to have a quick check on any servers connections count status and performances…
I can get it working for sys stats but no wowza infos… seems to be jmx communication buggy!
if i try 2.1.1 ami it’s so easy to get it all working
but 2.1.2 in no fun!:mad:
i failed on 6 retry from small to large instances…
As described here I get the Network and System graphs, but nothing for Wowza. It has been enabled for about 24 hours now and had over 100 sustained connections (according to /connectioninfo).
if i force my instance to start on us-east-1c … bingo!
instant reporting (few sec) of my streaming…
may be a zone problem?!
AMI ID: ami-26c62d4f
did someone changed the ami?.. or my brain? it looks ok now after starting 5 instances on Zone a c d… cant get zone b to start!
so… i am happy for now!
Do you know which instance had the problem initially? Could that have been zone B and forcing it out of B fixes that? Or does it need to be not-zone-B and forced into a zone. (clear?)
My instance is in Zone A, but if I remember EC2 correctly, my zones can be different than your zones (hence why they are just given generic letters).
We use wowza EC2 and cacti is enabled and available as a private ami on our s3.
The problem is that on the control panel of cacti, on Default Tree -> Wowza Media Server, on all the graphs we get “nan” on Current, Average and Maximum and the graphs are empty.
We restarted wowza after assigning elastic ip but the problem persists…