Discussion on log-parser-commands-for-fr-3

[bill[y]]

Hey Charlie, I'm likely missing something, but I can't see how to edit
this page. I just got a copy of the book Log Parser Toolkit and I was
going to post some info and a report, when finished. No rush ...

best,
bill

[charlie arehart]

Bill, when you connect to the FR group site
(http://groups.google.com/group/fusionreactor?hl=en), do you see among the
links on the right one that says "edit my membership" or one that says "join
this group"? If the latter, then you are either not logged into Google
Groups or are logged in with an address which is not the same one on which
you receive these group messages. You must be signed in with that account to
be able to edit the page:

http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-
3?hl=en

/charlie

[bill[y]]

Thanks, Charlie. I see "Edit My Membership" and I have been able to
post messages as well as comment _on_ this page, obviously. On my own
Google Group, MXUnit, an "Edit this page" button is available for
pages, but according to Google's Group Settings > Access, it seems
that for creating pages, there are two options, managers or members.
They don't have an access setting for editing pages. Is it possible
this setting is set to managers with the FR group?

bill

[charlie arehart]

Doh! That was it. Very hidden little option, but I finally found and
corrected it. Sorry.

/charlie

-----Original Message-----
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com]
On Behalf Of bill[y]
Sent: Thursday, March 20, 2008 5:44 AM
To: FusionReactor
Subject: FusionReactor Group: Discussion on log-parser-commands-for-fr-3

[bill[y]]

Hi,

I added a new query that uses a sql file and dynamic parameters. It
queries the crashprotection log between two given dates.

bill

Click on http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-3
- or copy & paste it into your browser's address bar if that doesn't
work.

[bill[y]]

I added a snippet that illustrates how to upload FR logs to a SQL
Server db.

[charlie arehart]

I updated the page so that it stands alone better, for those who may
be directed to it (as I often do). I also rearranged it so that later
contributions (by Bill) are now at the bottom of the page (so it flows
better for a first-time reader, since his builds on stuff I'd put in
originally.) I also added text asking that future contributions please
be placed below the current content.

[charlie arehart]

It's curious that this note came to the list with no more info. What a
bummer. It was a comment I'd made upon updating the google page on using
FusionReactor and LogParser together:

http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-
3

I put the comment in a comments area at the bottom of the page after
revising the document, just in case anyone reading it may have been
interested. I didn't expect it to send the comment to the list, here. I'd
have at least thought if it would include the URL, as otherwise it stands
out kind of curiously on its own. :-)

/charlie


-----Original Message-----
From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com]
On Behalf Of charlie arehart
Sent: Tuesday, March 10, 2009 1:43 PM
To: FusionReactor
Subject: FusionReactor Group: Discussion on log-parser-commands-for-fr-3

[bill[y]]

I added some info about "Frantic", a minimal Ant task wrapper for
LogParser I wrote last year. Though it's a hack, it's what I use at
work to get FR (and other) log data.

[charlie arehart]

In case anyone's wondering, Bill's comment here actually comes to the list
automatically based on an edit he did to the page referred to below his
comment:

http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-
3

That's a page that I created couple of years ago, and he and I continue to
add to it (anyone's welcome to). Sadly, the Google Groups "page" feature,
where we're editing it, offers a place at the bottom for a comment, whenever
we update it, and that comment's sent to the list. I got caught by it too,
once.

The problem is that we're just offering a comment to track what change we
made, thinking it may be stored for viewing with the document, and not
realizing it's sent to the list. I think it's an unfortunate choice Google
has made: if they would just add a preface to the email before showing the
comment, it would make sense, as otherwise it lacks context when it shows up
"out of the blue" on the list. Even the goofy subject line they create
really doesn't suffice.

Anyway, just wanted to explain for list members, who may see these once in a
while.

Bill, you may notice there's an option there to "skip this" step when you
publish a change. It's a shame they don't let us track the comment but not
email the group. Just doesn't work that way. :-(

/charlie

PS If you're reading this far and have still not looked at using the free
LogParser tool to help analyze FusionReactor (and other) logs, do take a few
minutes to check out that page above. The tool's features are pretty
amazing, and the page offers specific statements to use with the tool
against FR logs.

> -----Original Message-----
> From: fusion...@googlegroups.com
> [mailto:fusion...@googlegroups.com] On Behalf Of bill[y]
> Sent: Monday, June 29, 2009 10:47 PM
> To: FusionReactor

[Charlie Arehart]

I've made an update/correction to the logparser commands document and
just wanted to point it out here.

Some readers will know that I had created some time ago a page that
offers Log Parser commands for working with the FR logs. It's at
http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-3
(where Bill Shelton has offered some updates as well).

Well, I discovered a bug in the example showing how to show data from
"yesterday". The logparser function used in calculating "today"
happened to return its date/time as UTC time. But the FR dates are in
the local time of your server. As such, if there was a few hour
difference between those, the log parsing command would not work if
run within that few-hour window. The updated command will work
correctly all the time.

[Charlie Arehart]

For those familiar with the page of LogParser scripts for
FusionReactor (http://groups.google.com/group/fusionreactor/web/log-
parser-commands-for-fr-3), I wanted to share with the list that I've
updated it.

First, I've added various new scripts in recent months. I've not
generally notified the list of the change.

But more important, I want to point out that I corrected a minor error
in some that have existed for a long time. In any of those that
produced reports on an hourly (or per minute) basis, they used a
quantize function which it turns out might produce unexpected results
in some situations. I finally investigated and resolved the bug, with
a correction to the affected scripts (about 4 of them). If you'd used
them previously and found some odd results, the correction should
resolve that.

For those interested, the technical details of the solution were that
I had mistakenly offered originally a timestamp format (for the time
field) that ended in one L (".l") rather than two (".ll"). The latter
is necessary for a zero-leading millisecond value and the FR log
records do use that in the time column. I hadn't noticed that
originally so again, the scripts didn't work as expected sometimes.
Problem solved. :-)

But if you haven't been to the page in a while, you may be surprised
by all the useful log parser scripts available to analyze FR logs.

Even so, all this pales in comparison to what's possible with the new
coming FusionAnalytics, separately purchased but available now in
beta. Check that out, too, at http://www.fusion-analytics.com/fa/.

[Patrick Sauter]

Thanks for the update, Charlie.  I'm a big fan of using the log parser, and am especially glad to hear about FusionAnalytics, and am anxious to try it out.

So, I take it the FusionAnalytics beta isn't publicly available?  Or am I just not looking in the right place?

--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To post to this group, send email to fusion...@googlegroups.com.
To unsubscribe from this group, send email to fusionreacto...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fusionreactor?hl=en.

[charlie arehart]

Thanks for the kind regards on the LP page. I’[m not sure about how the beta signup process is working. Perhaps it’s that those who choose the option there to “receive news” are then contacted as new beta testers are added.

Sadly, the Intergral folks are generally off this week for a holiday week in Germany, so we may get only sporadic answers from them.  :-)

/charlie

[Gianna Benson [FusionReactor Team]]

Those that expressed interest in FusionAnalytics by signing up for our
FusionAnalytics newsletter received an invite to the FusionAnalytics
beta.

The beta is currently being evaluated by our first round of testers!

People can sign-up to receive news about FusionAnalytics through our
online form at http://www.fusion-analytics.com/labs/signup.cfm.

If anyone has any other questions regarding the FA beta, please let us
know.

/Gianna

On Apr 6, 12:32 pm, "charlie arehart" <charlie_li...@carehart.org>
wrote:

> Thanks for the kind regards on the LP page. I'[m not sure about how the beta
> signup process is working. Perhaps it's that those who choose the option
> there to "receive news" are then contacted as new beta testers are added.
>
> Sadly, the Intergral folks are generally off this week for a holiday week in
> Germany, so we may get only sporadic answers from them.  :-)
>
> /charlie
>
> From: fusion...@googlegroups.com [mailto:fusion...@googlegroups.com]
> On Behalf Of Patrick Sauter
> Sent: Monday, April 05, 2010 8:24 AM
> To: fusion...@googlegroups.com
> Subject: Re: [fusionreactor] Correction and updates to
> "log-parser-commands-for-fr-3"
>
> Thanks for the update, Charlie.  I'm a big fan of using the log parser, and
> am especially glad to hear about FusionAnalytics, and am anxious to try it
> out.
>
> So, I take it the FusionAnalytics beta isn't publicly available?  Or am I
> just not looking in the right place?
>

> On Sat, Apr 3, 2010 at 11:01 PM, Charlie Arehart <char...@carehart.org>

> wrote:
>
> For those familiar with the page of LogParser scripts for
> FusionReactor (http://groups.google.com/group/fusionreactor/web/log-

> <http://groups.google.com/group/fusionreactor/web/log-%0Aparser-comman...
> -fr-3>

> parser-commands-for-fr-3), I wanted to share with the list that I've
> updated it.
>
> First, I've added various new scripts in recent months. I've not
> generally notified the list of the change.
>
> But more important, I want to point out that I corrected a minor error
> in some that have existed for a long time. In any of those that
> produced reports on an hourly (or per minute) basis, they used a
> quantize function which it turns out might produce unexpected results
> in some situations. I finally investigated and resolved the bug, with
> a correction to the affected scripts (about 4 of them). If you'd used
> them previously and found some odd results, the correction should
> resolve that.
>
> For those interested, the technical details of the solution were that
> I had mistakenly offered originally a timestamp format (for the time
> field) that ended in one L (".l") rather than two (".ll"). The latter
> is necessary for a zero-leading millisecond value and the FR log
> records do use that in the time column. I hadn't noticed that
> originally so again, the scripts didn't work as expected sometimes.
> Problem solved. :-)
>
> But if you haven't been to the page in a while, you may be surprised
> by all the useful log parser scripts available to analyze FR logs.
>
> Even so, all this pales in comparison to what's possible with the new
> coming  FusionAnalytics, separately purchased but available now in

> beta. Check that out, too, athttp://www.fusion-analytics.com/fa/.

>
> --
> You received this message because you are subscribed to the Google Groups
> "FusionReactor" group.
> To post to this group, send email to fusion...@googlegroups.com.
> To unsubscribe from this group, send email to
> fusionreacto...@googlegroups.com

> <mailto:fusionreactor%2Bunsu...@googlegroups.com> .
> For more options, visit this group athttp://groups.google.com/group/fusionreactor?hl=en.

[Charlie Arehart]

Folks, just wanted to note that I've added a new report to the page
showing examples of LogParser scripts for use with FusionReactor.
(Actually, I've added others in recent months, but haven't made a
notification like this, so there are other "new" ones that may
interest you.)

This latest one, called "Total Number of Requests, per day, per
domain", does what it says, and can be useful if you ever have need to
perform some management task that depends on knowing what domains are
being hit most often within your server. It can also be useful simply
to see how many requests really are hitting your server, per day, per
domain. It can often be a surprise (given spiders, bots, hackers,
monitors, and more.)

To see the page of all the scripts, click on
http://groups.google.com/group/fusionreactor/web/log-parser-commands-for-fr-3