Flash Communication Server Logging : New Flogger
We are releasing a slightly updated version of our Flash Communication Server bandwidth monitoring tool (Flogger). This version has not been fully QAed by us and is thus not support by Macromedia. However, we wanted to get it out to developers as soon as possible.
It’s basically the same old Flogger, but now works with servers that have multiple vhosts.
The old Flogger collected stats from the default, main vhost: _defaultVhost_. If a server had multiple vhosts (usually only in ISP situations like MediaTemple) they could not get usage info on the applications running under other vhosts.
This version of Flogger asks the server for a list of the installed vhosts via a custom config tag in server.xml. It then connects as an administrator to each of these vhosts, and gathers information about the applications, bandwidth usage, etc.
The reporting is similar to the earlier version as well, but it has a new listbox for the various vhosts on the machine and a user can limit the reports to a particular vhost or applications from the vhost.
Flogger should work the same as before for single, default vhost servers.
Download Flogger 1.1 (unsupported).
You can read more about Flogger here. Note, that this document does not cover Flogger 1.1.
Thanks to every one on the Flash Communication Server team for making this happen.
Whoooweeee!! It might not be all that I wanted, but then again, still a step forward. Now to just get the data out of the swf and into a database and we will be closer.
Thanks guys, and good work.
Jason Key
Jason Key
9 Feb 03 at 10:45 am
We have just finished testing your Flogger 1.1 and it works exactly as it should. The Flogger collects data for each of the vHosts. After logging into the Flogger you can choose the vHost listed on the bottom left corner, which then displays its applications in the neighboring box from which it creates a report for its usage. We did not run into any problems with this, you guys have done great work.
We tried this on a test server with only 3 simultaneous vHosts. Has anyone tried it on a larger scale?
We want to take this data and compile it into weekly and monthly data easily available for each vHost client. The detailed information you provided along with this release will also help us.
This is a definitely a great admin tool and a huge step in the right direction. Again, thank you for your excellent work.
Greatfully,
Richard Blakely
Influxis
richard@influxis.com
Richard Blakely
14 Feb 03 at 2:27 pm
Might be a little late on the action here – but it seems that Flogger still doesn’t jive with multiple adapters each having applications in seperate application directories. What would be my resolve?
a) Just putting all the applications in the same application directory (hence sharing the same /admin dir)
OR
b) Modifying the Flogger.asc file each time I use it to use the administrator User/Pass for the adapter.
Both give me acid reflux. Feedback?
Shawn
20 Jun 03 at 11:58 am
Is there any way to view the output of “trace” statements on the server? The Flash MX NetConnection Debugger never seems to work (sometimes it does, but rarely).
The Flash Log Player on the same page as Flogger is worthless since you have to keep creating a report.
I don’t know why they just don’t show the trace output as they happen. It shows them on one line in that little window, why don’t they just show the whole thing!
I know it can get large, but I’m just doing small development right now. Macromedia sure makes this very developer un-friendly
Chad
21 Aug 03 at 1:09 pm
Jason Key, where are u from? I have seen where u have fixed several different things and thought i would check and see if u lived i my area…..
Linda
13 Jan 04 at 4:49 pm
Hi, I’ve brought some modification to the Flogger 1.0 and 1.1 .
Flogger seemed to still make a mistake with calculations of bandwidth used.
Here is a link to the fixed version of Flogger that I’ve corrected: http://flogger.is.dreaming.org/
Fredz./
Frédéric v. Bochmann
8 Jul 05 at 4:02 pm
Hi, I am having a problem with all versions of the Flogger on CentOS3.4.
The application appears in the app inspector and I can log in normally but it will not write the BandwidthInfo files into the streams/_definst_ directory.
The only server configuration item that may be unsual is that the server ip and admin is not on 127.0.0.1 but specified at 205.xxx.xxx.xxx – i have also set this in the Flogger.asc but it still doesn’t seem to work.
If i copy a server access log file (which is written as expected in the admin folder) into the Flogger folder, the flogger.swf can access and attempts to read it (but doesn’t make sense of it of course).
All permissions on all folders are set to nobody and the server runs as nobody. General Access logs appear to be written as root.
Any help would be appreciated.
thanks
Hash
Hash
5 Oct 05 at 12:34 am