Jeremy Wadsack wrote:
> So, we generate ASCII reports upon request
> and email them to the person.
>
> Doing so would mean running analog at the time the client wants to
view
> the stats, which is probably a peak hour. Instead we set up a batch
to
> run analog on a nightly basis with a configuration for each client.
Then
> we just point the client to the location of the HTML pages.
>
> We have a simple program that they run to generate month to date, or
> various past months. It will send the report to a given email address
for
> the time period in question.
Is this program specific to your system or could it be ported to others?
I think it would make a really useful add on for analog. I assume it's
written in 'C' or Perl and designed for Unix (i.e. uses sendmail). Could
it work n Mac or Windows?
It's written in perl. I can't give it away since it's a "value add" here,
but the basic concept is that you put together some canned configuration
files (last month, last week, month before last, month to date, that kind
of thing). Things missing would be the LOGFILE, the various URL items
(hostname, host url, etc.). Think of the missing stuff as "customer
specific data." When the customer executes the script, it takes the canned
file, adds to it the user specific data, and generates a unique
configuration script (I use PID to make sure the thing is reasonably
unique), and then fires off a second script which invokes analog with the
+g option (points to a configuration file). This writes to a similarly
named output file. When analog has done its work, I read the output file
into sendmail (good call, that), sending it to the indicated email address.
I've utilized this to generate reports for Apache, Netscape, and JWS (of
all things, whose braindead log files still upset me no end, but I hear IIS
and it are alike in this). And, it's pretty easy to add to your
"run-analog" script a bit where it sees if analog is already running, and
then sleeps some period of time before checking again. Or, your script
could generate some kind of semiphore. There's lots of ways to handle this
aspect of it.
Heck, with the help of Stephen, I got it looking at xferlog output as well
:)
> From what I've heard, I think this is the more common solution. But
then
> analog only recently acquired the form interface, so maybe that is
> because this was the only solution.
>
> >From what I know, Analog has had a form interface since 1.x, or was
capable
> of being run from CGI since that time. I know I've been doing that for
> quite some time.
>
Oops, I stand corrected. I'm kinda new to analog, but that was the
impression I got from people use of anlgform.cgi.
The anlgform.cgi is reasonably new. It was called something else (memory
fails me at this point) in earlier versions. And, you had to specifically
do a 'make form' or something like that which wasn't all that obvious (at
least, when I was new to analog, it wasn't obvious). Heck, it was probably
in the README, but we all know the instructions are the last things we
engineers look at :)
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
