Did you follow the setup setups in the Wowza EC2 guide. You have to uncheck a box and save. See the “Monitoring the Wowza Media Server on EC2 using Cacti” chapter.
On the “Management: Devices” page click the “Localhost” device in the “Description” column.
Uncheck the “Disable Host” setting in the “General Host Options” section of the page. Then click the “Save” button at the bottom of the page.
I tried it with that same AMI and it worked for me. Are you sure you are following the steps to enable in the EC2 guide? I guess it could be bad luck with 2 instances in a row, but I cannot replicate the problem.
I fired up a new instance this morning and Cacti detected and graphed RTSP live streams fine. Please send an email with the details of what you’re seeing to support@wowza.com and we’ll get things sorted out.
I tested the EU-Instances and Cacti is graphing correctly for me.
There are two common issues when using Cacti to watch out for. One is that the Cacti system checks for connections once every 60 seconds or so. If you watch 45 seconds of a stream then stop the system may not log you as a viewer. The second is the graphing time range is not good about reseting to the current time. If you load the graph page and select ‘last half hour’ as your time frame it loads the current time and last half hour. But if you go to lunch and come back, even if you refresh the page the system will still have the old ‘half-hour’ times loaded. In these cases you must manually set the time frame you wish to view.
All seems well with Cacti monitoring on my EC2 instance and we have a couple of streams running 24/7 but no streams show up in the graph Localhost - Wowza Server - Stream ([name]) Connections. All client and server connections show up fine.
Is this graph template expected to automatically graph all current streams and substitute the field name automatically or is there a manual substitution?
If manual please explain procedure. I would like to monitor activity stream by stream.