Re: [analog-help] logrotate
Just to let you know that this works nicely :-) Brian > > > Brian Clifton wrote: > > > Nice thinking Jeremy :-) > > > > Only one small caveat (question)...Wouldn't this destroy the ability to > > keep x number of reports before over-writing?? > > > > I keep 4 weeks worth of reports, so after report.html.4, logrotate > > starts over-writing. I haven't tried yet, but I think re-naming would > > stop this. How about cp?? > > > > Yeah, logroate pushes each log down the stack, so you'd need to do > something like > > cp report.html.1 1.report.html > cp report.html.2 2.report.html > cp report.html.3 3.report.html > cp report.html.4 4.report.html > > after the logration is completed > > > Jeremy Wadsack > Wadsack-Allen Digital Group > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] logrotate
Nice thinking Jeremy :-) Only one small caveat (question)...Wouldn't this destroy the ability to keep x number of reports before over-writing?? I keep 4 weeks worth of reports, so after report.html.4, logrotate starts over-writing. I haven't tried yet, but I think re-naming would stop this. How about cp?? Best regards, Brian > > > Brian Clifton wrote: > > > Dear All > > > > I am currently using crontab/logrotate to rotate my logfiles and Analog > > reports. However the syntax format appends a number to the filename e.g. > > > > report.html -> report.html.1 etc... > > > > Does anyone know of a way to change this e.g. 1.report.html > > mv report.html.1 1.report.html > > > You can add postrotate commands to the end of the section of your > logrotate.conf (or logrotate.d/*) configuration file. > > HTH > > Jeremy Wadsack > Wadsack-Allen Digital Group > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
[analog-help] logrotate
Dear All I am currently using crontab/logrotate to rotate my logfiles and Analog reports. However the syntax format appends a number to the filename e.g. report.html -> report.html.1 etc... Does anyone know of a way to change this e.g. 1.report.html That way all rolled over reports could be viewable in the web browser. Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] pointing analog to configuration file
Use the following /usr/bin/analog -G +g/home/httpd/path_to.cfg Also I wrote a HOWTO on rotating logfiles/Analog reports. Try: http://www.sussexfind.co.uk/omegadm/tips/HOW-TO-ROLLOVER.htm Best regards, Brian > I know it might sound silly, but I can not seem to figure out how to point > analog to a file... say I have a number of virtual hosts in > /www/siteone.com /www/sitetwo.com > > and they have a analog.cfg in their directories. When I run from CRON I'd > like to say analog /www/siteone.com/analog.cfg but it's not working. > Anyone? > > Denis Voitenko > Qode.com Internet Developer > Tel: (954) 484-3191 x 153 > Fax: (954) 484-2933 > > --- Brian Clifton, Technical Director Omega Digital Media Ltd Phone: +44 (0) 1444 410202 Fax: +44 (0)1444 412909 E-mail: [EMAIL PROTECTED] http://www.omegadm.co.uk/ This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] DNS
If properly setup, your DNS will automatically forward enquiries of domains it doesn't know about to the next DNS in the chain - that's the beauty of the DNS system :-) Best regards, Brian > Are there any public DNS services that might "know" more names > than one's ISP? > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > -------- > > > --- Brian Clifton, Technical Director Omega Digital Media Ltd Phone: +44 (0) 1444 410202 Fax: +44 (0)1444 412909 E-mail: [EMAIL PROTECTED] http://www.omegadm.co.uk/ This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] REFEXCLUDE
> > Something I thought could not be set... How do I alter the floor?? > > HOSTFLOOR 1r. See docs/othreps.html#FLOOR and related report docs. Thanks Jeremy - couldn't find it for looking! > > > REFEXCLUDE http://mps.com/* will throw away the first line, and the > > > general summary will record 1 hit, and one unwanted entry. The HOST > > > report will only show one HOST - 6.7.8.9, because you have totally > > > excluded the entry from 1.2.3.4 (because it was referred from > > > http://mps.com) > > > > It sounds like you are saying I don't need this if I use HOSTEXCLUDE > > *.mps.*?? > > No HOSTEXCLUDE will exclude all requests made from the host, probably just > the webserver, but maybe all requests in the company (depends how your DNS > is setup). > > REFEXCLUDE will exlcude all request made from links within the site from > all reports and all results. OK, makes sense. Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] REFEXCLUDE
> Brian Clifton wrote: > > >OK, so as I am not trying to be clever and use specific reports, then all > >I need are HOSTEXCLUDE and REFEXCLUDE > > > >My thinking (hope) for using the later is that I want to see what > >external pages e.g. search engines are referring visitors to us. > > In which case, you may find the REFSITE report useful, rather than > the referrer report OK, it looks like I should have REFERRER ON and REFSITE ON. My reason behind using both is so that REFSITE ON will give me the Search Engine address e.g. altavista.com, while REFERRER ON will give me the full url including the query term e.g. altavista.com?search=a_keyword_phrase. > I think there may still be some confusion about what you want to do, and > what you need to do to achieve it. Most probably, but you are definitly helping :-) > Let's take these 2 imaginary log entries: > 1.2.3.4 - - 12:34:56 GET /folder/page.htm 200 "http://mps.com/links.htm" > 6.7.8.9 - - 06:54:32 GET /subdir/index.htm 200 "http://yahoo.com" > > HOSTEXCLUDE 1.2.3.4 will throw away the first line - Analog will > report only a single hit in your log, and 1 unwanted entry. The > request report will only show one request - the request for > /subdir/index.htm. The Referrer report will only show 1 entry, for > http://yahoo.com (assuming you've set your floor low enough). Something I thought could not be set... How do I alter the floor?? > If 1.2.3.4 resolves to user1.mps.com then HOSTEXCLUDE *.mps.com will also > throw away that line. (HOSTEXCLUDE http://*.mps.com won't do anything at > all, as far as I know - HOSTs won't match a string that starts with > "http://"). OK, I have changed my HOSTEXCLUDE *.mps.*, as for some sites we have multiple domains e.g. mps.com, mps.net etc. > REFEXCLUDE http://mps.com/* will throw away the first line, and the > general summary will record 1 hit, and one unwanted entry. The HOST > report will only show one HOST - 6.7.8.9, because you have totally > excluded the entry from 1.2.3.4 (because it was referred from > http://mps.com) It sounds like you are saying I don't need this if I use HOSTEXCLUDE *.mps.*?? > REFREPEXCLUDE will just exclude the first line from the Reference > report, so the only entry on the REFERRER report will be yahoo.com. > The general summary will record 2 hits, and no unwanted entries. The HOST > report will show 2 hosts, the REQUEST report will show 2 files were > requested Ok, understood. I have removed this. > (By the way, please try to reply after the text you are quoting, rather > than before). Hope you don't mind my mix 'n' match on this one?? Best rgeards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] REFEXCLUDE
Hi Jeremy OK, so as I am not trying to be clever and use specific reports, then all I need are HOSTEXCLUDE and REFEXCLUDE My thinking (hope) for using the later is that I want to see what external pages e.g. search engines are referring visitors to us. Best regards, Brian > > > Brian Clifton wrote: > > > Will HOSTEXCLUDE, HOSTREPEXCLUDE, REFEXCLUDE, REFREPEXCLUDE be enough to > > eliminate all internal referrers/hosts from all reports/analysis or do I > > need all the EXCLUDE commands e.g. > > > > DOMEXCLUDE, FAILREFEXCLUDE etc. > > The commands HOSTEXCLUDE, REFEXCLUDE, etc. remove all lines from the input > that contain those values. So > > HOSTEXCLUDE http://www.mpswholesale.* > > Will remove all requests made from that host from ALL reports. Similarly, > > REFEXCLUDE http://www.mpswholesale.* > > Will remove all requests that were referred by the site. In essence it > will leave only you 'entry pages' the pages people first came to (or typed > in, or selected from bookmarks, etc.). > > The HOSTREPEXCLUDE, DOMEXCLUDE, REFREPEXCLUDE, etc. commands will remove > those entries from the specified reports. So > > REFREPEXCLUDE http://www.mpswholesale.* > > Will remove all internal referrers from the referrer report. But will not > remove traffic generated by those requests from other reports. > > HTH, > > Jeremy Wadsack > Wadsack-Allen Digital Group > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] REFEXCLUDE
Hi Stephen Sorry I am replying the wrong (deleted by mistake) message... I take it *.mpswholesale.* would also equally be correct to http://www.mpswholesale.* Will HOSTEXCLUDE, HOSTREPEXCLUDE, REFEXCLUDE, REFREPEXCLUDE be enough to eliminate all internal referrers/hosts from all reports/analysis or do I need all the EXCLUDE commands e.g. DOMEXCLUDE, FAILREFEXCLUDE etc. I ask because I will be doing a comparison with the latest WebTrends and want to make sure I will be comparing like with like. In WT, my options are to exclude referrer and user address. In both cases these will be http://www.mpswholesale.* Of course I will report to the list my results. Best regards, Brian > On Tue, 1 Aug 2000, Jeremy Wadsack wrote: > > > > > > > Brian Clifton wrote: > > > > > HOSTEXCLUDE www.mpswholesale.*,194.70.240.235,*u-net* > > > REFEXCLUDE www.mpswholesale.*,194.70.240.235,*u-net* > > > > The INCLUDE/EXCLUDE commands do not support comma-separated lists. > > Yes they do. > > -- > Stephen Turner http://www.statslab.cam.ac.uk/~sret1/ > Statistical Laboratory, Wilberforce Road, Cambridge, CB3 0WB, England > "The new operating system will recover more easily from system crashes." > (Microsoft, aiming high with Windows Millennium) > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
[analog-help] REFEXCLUDE
Hi there! I wish to exclude a domains internal references to pages within itself and so have the following 2 lines in cfg: HOSTEXCLUDE www.mpswholesale.*,194.70.240.235,*u-net* REFEXCLUDE www.mpswholesale.*,194.70.240.235,*u-net* mpswholesale is no-where in the list of Hosts Report :-), but the Referrer report is full of e.g. www.mpswholesale.com/side.htm www.mpswholesale.com/main.htm etc... Am I missing something?? Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] Caching and Rotating
If anyone wants the HOWTO from me, post to me personally at [EMAIL PROTECTED] The only condition is that you should give me some feedback on it!! Best regards, Brian > > > Devanesan wrote: > > > I am a new user of analog. I have configured Analog4.03 for my company. > > I want to include the functions of Caching and Rotating in it. So that > > analog runs only the new entries in the logfile and stores the result in > > a common file called report.html. This is to prevent analog from running > > the same old log contents, every time as it runs as a cron job. > > > > Kindly tell me a way of how to achieve it. Should I use any different > > package for this or does Ananlog4.03 has an in built facility for > > this > > Caching is covered in detail in your Analog documentation. See > docs/cache.html. > > Rotating logfiles needs to be done by an external program (like > logrotate). I don't see the HOWTO on rotating yet. I suspect it will be > posted shortly. > > Jeremy Wadsack > Wadsack-Allen Digital Group > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] Caching and Rotating
I wrote a HOWTO on rotating logfiles which Stephen has. Don't know if he has published it though! Best regards, Brian > Hello, > > I am a new user of analog. I have configured Analog4.03 for my company. I > want to include the functions of Caching and Rotating in it. So that > analog runs only the new entries in the logfile and stores the result in a > common file called report.html. This is to prevent analog from running the > same old log contents, every time as it runs as a cron job. > > Kindly tell me a way of how to achieve it. Should I use any different > package for this or does Ananlog4.03 has an in built facility for this > > Regards > Devanesan. > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
[analog-help] HOSTEXCLUDE
Dear All I have multiple domains for a client which point to different web sites (doorway pages) but log into one file. I wish to exclude the hosted sites from the Analog report except referrers. For example, one site hosted is http://www.site1.com and I do not want links from pages within this site to other site1 pages to be analysed. However, I do want to know if site2.com is providing visitors without analysing all site2-site2 links. Is this possible?? I am guessing not if using a single log file... Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] analyze on Cobalt Raq's (long)
> > I know need to work on the logrotate.conf and the site files in > > /etc/logrotate.d/ directory to get more data. Been reading and printing > > all night from the cobalt and analog list archives. I am using logrotate on RH6.1 - it took me a while to work it out and I am in the process of writing a HOWTO. This should be done next week. Send me your e-mail address and I will post you a personal copy - you can be the ginnea pig!! Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] vitual doms
Agreed - I use a combined log which colleagues tell me is good for ~200 domains on Apache/Linux. Of course how popular each site is will also be a factor. Best regards, Brian > > > Brian Clifton wrote: > > > Log each vdomain into its own log file and then run an instance of > > analog with its own config file for each virtual domain. The overhead is > > very small and this will keep the size of your log files manageable. > > > > Actually Brian, the overhead can become quite significant under Apache > when running a large number of virtual hosts (which may not be the case > here). This is described in the Apache docs, suggesting that you log all > domains together and split them externally. I think "a large number" is > probably around 100, but of course this depends on your hardware. :) > > > Jeremy Wadsack > Wadsack-Allen Digital Group > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] vitual doms
Log each vdomain into its own log file and then run an instance of analog with its own config file for each virtual domain. The overhead is very small and this will keep the size of your log files manageable. Brian > dear analogers, > I'm struggling again "against" virtual domains... > I would like to analyse it from one log file, without log splitting. > Sorry - but I do not understand the example file :-( > > Our actual log file format is > 203.77.126.62 - - [29/Mar/2000:09:08:46 +0200] "GET > http://www.pzvd.de:81/profiltext.gif HTTP/1.0" 200 859. > > We have domains like www.domain1.com, www.domain2.net > and we have sub domains sub1.domain1.com, sub2.domain1.com > > and... hrrmm... at least...a few "subdomains" in a sub directory, like > www.domain1.com/subdir1 > > is there any chance, to get them separated in a report file? > > thanks for any help > > > > Uwe Jandt > > atacama|Software > http://www.atacama.net > > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] FW: need help understanding logs/archiving reports
Are you enquiring about rolling over the server log files and analog reports? If so I have figured out a simple way which uses crontab and logrotate (RH6.1). I am in the process of writing a HOWTO for the Analog web site. In the mean time read up on the these programs/files to familarise yourself. The HOWTO will be ready next week! Best regards, Brian > > > I am very new to the log world (i.e., I know just about nothing about > > them). What I did was install analog and got it to run on one server. > > The log file belongs on another server, and I ftp to retrieve it, then > > run the analog report. That part works. I haven't tried to get the > > form to run on the system yet. (Will try to install Report Magic soon.) > > > > What I would like to do is automatically generate daily, weekly, > > monthly, quarterly and annual statistics for the website. However, I > > don't know how the log file process works, or how to write the script > > (in Perl or Unix shell?) that will do the storage and archiving of the > > log files on the report server, etc. (I'm hoping this makes sense to > > someone.) > > > > Does anyone have a script they're willing to share out that can do this, > > or am I totally barking up the wrong tree? Any help you can give would > > be much appreciated. > > > > The log file is in CLF format, and I installed analog on an apache > > server, running on Solaris 5.6 OS. > > > > Thanks in advance, > > > > Geraldine Golveo > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
[analog-help] log rollover and analysis - HOWTO
Dear Stephen With the help of Karel Kerezman, we have a very nice and simple method for rolling over apache logfiles and running Analog by using crontab/logrotate on RedHat 6.1. Could I post a supplementary HOWTO for your site. It would be a simple alternative to Rebecca Minarik's script. Please forward any guidelines. Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Sorry Karel I hadn't realised 'cronolog' was part of logrotate - still my man logrotate has nothing on this!! Perhaps it not part of RH6.1 default install? Best regards, Brian > >Hi Josef > > > >I am still struggling with logrotate so I would be interested in anything > > you are doing with cronolog (can't find any docs on this!) > > > > You mean, outside of 'man logrotate'? > > Man pages are required reading for any core app you want to manipulate. This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] Apache Log format
This is a typical entry in my httpd.conf file: CustomLog /home/httpd/mydomain.com/logs/combined_log combined This tells apache to use a CustomLog format defined earlier in the file as 'combined' and store it a /home/httpd/ HTH, Brian > >I'm trying to generate some logs with analog. I get an error message > >saying > > [snippage] > > Yes it does... what's happening there is Apache is "defining" certain log > formats. Almost immediately thereafter should be another line: > > CustomLog /var/log/httpd/access_log common > > It may also read "combined" at the end, which is the one you want if > you're looking for Browser and Referrer data. What's going on here is a > two-stage process: Define the kinds of logs available, and assign one of > those kinds to a specific log file. > > You don't need a LOGFORMAT line in analog.cfg, Analog picks right up on > the Apache common and combined formats automagically. This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Josef I am still struggling with logrotate so I would be interested in anything you are doing with cronolog (can't find any docs on this!) Best regards, Brian > HI, > > how does logrotate compare to cronolog? Any ideas? > I have always thought that cronolog is the best for most situations... > > Thanks, > > Josef D. > > > On Mon, 22 May 2000, Karel Kerezman wrote: > > > >Thanks for your reply - The simpler the better...OK, I think I follow > > >your suggestion. Below I have listed my appended contents of > > >/etc/cron.daily/logrotate.conf. > > > > My /etc/cron.daily/logrotate file looks like this: > > > > #!/bin/sh > > > > /usr/bin/analog > > /usr/bin/logrotate /etc/logrotate.conf > > > > The log rotation is being handled by the logrotate utility, using the > > params given in /etc/logrotate.conf, and I'm running analog right ahead > > of that so logs aren't "in transit" when I'm trying to parse data. > > > > >Could I please ask you (or anyone) to knidly check if this is alright? > > >One thing in particular, the '/sbin/killall -HUP httpd' command is > > >given as an example in the man logrotate file. Is this required?? > > > > Basically what that command is doing is saying to httpd (the Apache > > daemon) in this case "Okay, let go of the files for a moment and > > reattach to them because you've got a fresh new log file to work with." > > The -HUP signal is designed to 'soft-restart' a particular process, > > generally used when there's been a change to its config file(s). > > > > > > > >---APPENDED TO THE BOTTOM OF LOAGROTATE.CONF--- > > ># system-specific logs may be configured here > > ># Added by BC 22/5/00 > > > > [snipped for space] > > > > >--- > > > > > >All I then need to do is set company-domains.cfg: > > >LOGFILE /home/httpd/company-domains.net/logs/combined_log.1 > > > > > >i.e. pointing to the rotated log file (which souldn't be compressed > > >until the next rotation)? If this is right, it is a very neat solution. > > > > I'm going to guess that you're dealing with virtual hosts? I freely > > admit that I have no experience in this area. I'm using only the stock > > access_log file that lives in /var/log/httpd as per the stock RedHat > > install. If I'm reading what you're doing correctly, though, it ought to > > work. Be prepared for someone much smarter than I am to offer a better > > suggestion, though. > > > > > > Karel P Kerezman > > Network Administrator > > Entercom Radio Portland > > KGON KKSN-AM/FM KNRK KFXX KRSK > > Visit the Lab: http://washuu.kgon.com > > > > -BEGIN GEEK CODE BLOCK- > > Version: 3.12 > > GO d- s: a- C++ UL P+ L E W++ N+++ o-- K- w--- > > O M V-- PS+ PE Y+ PGP t 5++ X-- R tv+ b+++ DI++ D++ > > G e h r+++ y > > --END GEEK CODE BLOCK-- > > > > > > This is the analog-help mailing list. To unsubscribe from this mailing > > list, send mail to [EMAIL PROTECTED] with > > "unsubscribe" in the main BODY OF THE MESSAGE. List archived at > > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] DNS Lookups
Paul Are you on a leased line or does your network support ping 'proxying'. As far as I know most proxy servers do not have the capability to proxy ping (icmp) packets. Best regards, Brian > I prefer using Analog to go through the web server logs but I can't get > DNS lookups to work. > > I'm using it on Win'98 analysing IIS logs but it won't resolve any DNS > lookups. As a point of note ping doesn't work either. I have a feeling > this is due to doing the lookups in a DOS window but not sure. > > Any advice on how to get DNS lookups to work and I've already tried > AnalogX QuickDNS as well with no luck. > > > All help appreciated, > > Paul > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Karel Analog has run OK according to cron.daily, but the logs are not rolling over! The only messages e-mailed to me are Analog warnings concerning empty reports e.g. Empty Search Word Report. Would you mind if I mailed you off-list concerning this? Best regards, Brian > Hi Karel > > > The answer to both of these questions is the /etc/crontab file. You are > > correct, cron does check every minute to see if there's something to run > > in the various crontabs (user and system). /etc/crontab, the system file > > (as it were), indicates which time of day/month/etc to run each of the > > "parts" in the various cron.X directories. Mine's set to 4:00am for the > > cron.daily contents. YMMV, as always. > > > > Got it! At last!! I couldn't find any info on the format of the crontab > file but a colleague of mind has passed this on from Novell's docs. > > # run-parts > 01 * * * * root run-parts /etc/cron.hourly > 02 4 * * * root run-parts /etc/cron.daily > 22 4 * * 0 root run-parts /etc/cron.weekly > 42 4 1 * * root run-parts /etc/cron.monthly > > Therefore my cron.daily is also set to run at 04:02 each day. Will let you > know if it works tonight... > > Thanks for all your help, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Fin I have changed the mail server MX record to mail.iddeo.es Your Spanish ISP will know what this means and can inform me if it should be different. Best regards, Brian > >Maybe I am missing something...I understand that within logrotate.conf > >you can schedule daily, weekly, monthly, but I thought (somewhere in the > >docs) that cron checks its files every minute by default and cron.daily > >was checked every day. Therefore putting analogue in this part would > >execute it every day, followed by rollovers as specified in .conf! You > >obviously don't have this so I am definitly missing something... > > [snip] > > >I am probably worrying over nothing... How have you specified 4am as a > >time to run? As cron is running every minute I was under the impression > >all logs would rotate at 00:01:00? > > The answer to both of these questions is the /etc/crontab file. You are > correct, cron does check every minute to see if there's something to run > in the various crontabs (user and system). /etc/crontab, the system file > (as it were), indicates which time of day/month/etc to run each of the > "parts" in the various cron.X directories. Mine's set to 4:00am for the > cron.daily contents. YMMV, as always. > > >I am Linux-adolescent myself, but as I get past each stage I always make > >a point of helping someone else on these discussion groups where I can. > >Feel free to mail me about linux stuff in general - it helps me learn > >too. > > > >Best regards, Brian > > Righto. We now return the analog list to its regularly scheduled chaos... > > > Karel P Kerezman > Network Administrator > Entercom Radio Portland > KGON KKSN-AM/FM KNRK KFXX KRSK > Visit the Lab: http://washuu.kgon.com > > -BEGIN GEEK CODE BLOCK- > Version: 3.12 > GO d- s: a- C++ UL P+ L E W++ N+++ o-- K- w--- > O M V-- PS+ PE Y+ PGP t 5++ X-- R tv+ b+++ DI++ D++ > G e h r+++ y > --END GEEK CODE BLOCK-- > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > --- Dr. Brian Clifton, Technical Director Omega Digital Media Ltd Phone: +44 (0) 1444 410202 Fax: +44 (0)1444 412909 E-mail: [EMAIL PROTECTED] http://www.omegadm.co.uk/ This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] WT vs. Analog (last post - promise)
> I don't want to get into some sort of 'WT is overly creative' flame war > here and waste everyone's time, so this will be my last post. You already have... > Okay, maybe pure twoddle was a bit wide of the mark - let's say > genetically modified twoddle 8). It is better to be simpler and accurate > than to be fancy. At best, the WT reports below are wrong, at worst > totally inaccurate and misleading. If your client came back to you and > asked you to explain the logic (and ergo accuracy) behind these reports > would you be totally at ease telling them? I know I wouldn't and that's > why I don't use the software. No these are not wrong - they are just guides. If you include them and make out they are gospel, then YOU are wrong. > pathways within site > entry page > exit page > visit length > page views per visitor session > first time users > etc etc > > For an explanation of why these are inaccurate > http://www.analog.cx/docs/webworks.html - have you actually read this? I > would hope that you're not sending out reports without having done > so The same explanations are available in the WT manual, have you read that? Both documents point out "might's, if's and but's" and these proviso's should be passed on to the client. For instance, I personally do not include pathways within site or entry pages as there are too many variables to make sense of this. However, exit page and visit length can be tightened down more. For example, if a requesting ip is not 'seen' again for a specified period - say 60 mins, you can reasonably assume that person has left the site. But as with all the stats (no matter how you analyse them) there is a margin of error. My point is simply that if the data used is from the same source then the basic stats should be the same. Analog is not better or worse than WT in my opinion because the resulting report data must be the same - unless one of them is inventing data! You are simply putting too much emphasis on the fact that WT has more config/graphing/table tools than Analog and calling this 'wrong'. It is the interpretation of data that is right or wrong, not the analysis program. This is also my last post on the matter! Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] unique visitors (daily, weekly, monthly)
> There was a post re: this matter two weeks agon when W*bTr*ends came up on > the list. Check the archives around May 10th for Jim Sander's strong > dismissal of the product's claimed reliability. I will have a read of this. > Report Magic will provide you all the fancy reports, graphs, and > desciptions that WebTrands does. It does not (yet) provide trends. This is why we use WT. > Installation is faily simple in Windows and Mac systems (although it > doesn't have a fancy InstallShield wizard). Installation on Unix systems, > the first time, is still unwieldy (yes, this is a known issue :). This is why we use (basic) Analog on the server Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] unique visitors (daily, weekly, monthly)
I have not done a direct comparision, but I am pretty sure as far as bare facts go they would be the same. If you have an example where WT has produced pure twoddle, please post. By 'detailed' I mean presentation wise. In my experience, marketing departments want clear and precise graphs/trends/percentage differences and this is what WT is good at - the report e-mailed as a word document is particularly powerful. I have not used Report Magic but I imagine both have strength's and weakeness. It really is 'try and see which is best for you'. Brian > Well here's my tuppence worth; > > I don't think that you can say that WebTrends is 'much more detailed' than > Analog. I do think you can say that WebTrends is vastly more 'creative' > than Analog. The reasons for this are beautifully outlined in the 'what > you can and can't do' section of the Analog site. I have found it to be > worth the effort to explain to clients why many of the apparently fancier > WT reports are utter twoddle. In my experience they are surprisingly > receptive! If you need graphical representations, then Report Magic has > been developed and is also free (and bloody quick too!). I hope your > marketing department goes for it (point them in the direction of the FAQs > on www.analog.cx)! > > Charl > > > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] unique visitors (daily, weekly, monthly)
I have used WebTrends for 2 years - its a great product, easy to use and a wealth of info presented in a trendy looking format. Customers are certainly impressed. One of the nicest parts is it can generate the reports as MS Word documents and e-mail them to your client - all automated of course. On the downside its not cheap and has a large overhead on resources when running. I use it on a standalone Win95 box, collecting log files from our ISP. Beware it won't generate Office2000 word reports on a Win95 box (apparently win98 is OK) I have only recently started using Analog, though our ISP runs it as default. The problem I had was I couldn't customise it as it belongs to the ISP. Now we are running our own Apache/Linux server for some of our clients. Analog offers a nice simple way of providing stats quickly, directly on the server. However, if a client required more detailed reports, I will use WT. Although WT is available for the server, I feel it is too much overhead (and too expensive!) Best regards, Brian > Brian, > > >I don't want to sound negative about Analog - its great as a general > >guide to what going on. But surely if you want detailed analysis for > >Marketers you need a more detailed(?) product i.e. WebTrends?? > > That's what I was considering a few mails back, but I'm not quite > sure about the actual accuracy of WebTrends vs. Analog. Seems to me > there's a whole lot of compromises behind WebTrends, apart from the > fact that it looks on "Sessions" rather than simple "File requests" > (like Analog). > > I would be very much interested in any online comparative studies of > the different tools available (not forgetting the fact that Analog is > absolutely free of charge (do we ever thank you enough, Stephen?))... Or > just a simple summary of the differences, so that I can convince my > marketing-department once and for all that I not only opted for the > cheapest solution when choosing Analog, but also the most honest (?). > > Regards, > Christian > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] unique visitors (daily, weekly, monthly)
I don't want to sound negative about Analog - its great as a general guide to what going on. But surely if you want detailed analysis for Marketers you need a more detailed(?) product i.e. WebTrends?? Brian > Hi Chad, > > >> >True, but the trouble is that some of us work in intense colaboration > >> >with marketers, and have daily demands for the number of visits, > >> > >> true. I do. > > > > i do also. in analog's "General Summary" theres a table saying > > "Distinct Hosts Served" ... but thats only for the entire span of > > time covered by the logs. is there any way for us to determine the > > number of disticnt hosts served on a daily, weekly and monthly basis ? > > If I get your question right you could do this by simply generating > time-limited reports (i.e. generate reports from a particular date to a > particular date). That's how we do it, at least. > > Regards, > Christian > > This is the analog-help mailing list. To unsubscribe from this mailing > list, send mail to [EMAIL PROTECTED] with "unsubscribe" > in the main BODY OF THE MESSAGE. List archived at > http://www.mail-archive.com/analog-help@lists.isite.net/ > > > This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Karel > The answer to both of these questions is the /etc/crontab file. You are > correct, cron does check every minute to see if there's something to run > in the various crontabs (user and system). /etc/crontab, the system file > (as it were), indicates which time of day/month/etc to run each of the > "parts" in the various cron.X directories. Mine's set to 4:00am for the > cron.daily contents. YMMV, as always. > Got it! At last!! I couldn't find any info on the format of the crontab file but a colleague of mind has passed this on from Novell's docs. # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly Therefore my cron.daily is also set to run at 04:02 each day. Will let you know if it works tonight... Thanks for all your help, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Karel Yes, I only signed up yesterday. I agree with your previous post - I will do as you have done and run analogue first and then do the rollovers in logrotate.conf. Will let you know how I get on tomorrow. > The reason it's in cron.daily by default is so that if you do want it > daily, you tell logrotate.conf so. The .conf file tells the logrotate > utility how often you want them rotated... so six days out of seven no > rotation takes place. No big deal, and you have the flexibility to change > that schedule if you want to. Check the logrotate docs for better info > that I can give... Maybe I am missing something...I understand that within logrotate.conf you can schedule daily, weekly, monthly, but I thought (somewhere in the docs) that cron checks its files every minute by default and cron.daily was checked every day. Therefore putting analogue in this part would execute it every day, followed by rollovers as specified in .conf! You obviously don't have this so I am definitly missing something... > It's a very-soft restart, along the lines of a "reload your configs, > please" instead of a "close out and restart, please." Having said that, > there's a reason this stuff happens at 4am or thereabouts. ;) I am probably worrying over nothing... How have you specified 4am as a time to run? As cron is running every minute I was under the impression all logs would rotate at 00:01:00? I am Linux-adolescent myself, but as I get past each stage I always make a point of helping someone else on these discussion groups where I can. Feel free to mail me about linux stuff in general - it helps me learn too. Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Ah, I see now - slightly different from what I had thought. > My /etc/cron.daily/logrotate file looks like this: > > #!/bin/sh > > /usr/bin/analog > /usr/bin/logrotate /etc/logrotate.conf > > The log rotation is being handled by the logrotate utility, using the > params given in /etc/logrotate.conf, and I'm running analog right ahead of > that so logs aren't "in transit" when I'm trying to parse data. This makes sense. Yes, I will be dealing with vhosts. So by your method I would have: #!/bin/sh /usr/bin/analog -G +g/path_to_cfg_file/vhost1 /usr/bin/analog -G +g/path_to_cfg_file/vhost2 # etc. /usr/bin/logrotate /etc/logrotate.conf and in logrotate.conf I would rollover both the analog combined_log.html files and the combined_log files? If the above syntax is in: /etc/cron.daily/logrotate, does that mean your analog is running every day? Therefore placing in /etc/cron.weekly/logrotate, makes it weekly?? One further question, does -HUP actually disable httpd? I am just thinking that if I had say 100 sites hosted, doing 100 x -HUP signals could be a significant downtime? Thanks for your help. Best regards, Brian This is the analog-help mailing list. To unsubscribe from this mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe" in the main BODY OF THE MESSAGE. List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Further thoughts...
I will also need to rollover the analog .html files. My problem here (if
I am on the right track!), is that the .html rollover must take place
AFTER the log_file roller to keep the extensions in sync. Is logrotate
run in chronological order i.e. the next job only starts after prceeding
one finishes??
If so, my updated logrotate.conf is:
--
# system-specific logs may be configured here
# Added by BC 22/5/00
# rotate log file:
/home/httpd/company-domains.net/logs/combined_log {
create
rotate 7
daily
errors [EMAIL PROTECTED]
postrotate
/sbin/killall -HUP httpd
analog -G +g/home/httpd/cgi-bin/company-domains.cfg
endscript
delaycompress
}
# I may need a time delay here?
# rotate Analog file:
/home/httpd/company-domains.net/logs/combined_log.html {
# don't create new log file as analog does this.
nocreate
rotate 7
daily
errors [EMAIL PROTECTED]
endscript
nocompress
}
--
In this way:
rollover combined_log---> combined_log.1
analog input(combined_log.1) ---> combined_log.html
rollover combined_log.html ---> combined_log.html.1
Therefore combined_log.1 will always match with combined_log.html.1
Hope I am right!!!
Best regards, Brian
> Hi Karel
>
> Thanks for your reply - The simpler the better...OK, I think I follow your
> suggestion. Below I have listed my appended contents of
> /etc/cron.daily/logrotate.conf.
>
> Could I please ask you (or anyone) to knidly check if this is alright? One
> thing in particular, the '/sbin/killall -HUP httpd' command is given as an
> example in the man logrotate file. Is this required??
>
>
> ---APPENDED TO THE BOTTOM OF LOAGROTATE.CONF---
> # system-specific logs may be configured here
> # Added by BC 22/5/00
>
>/home/httpd/company-domains.net/logs/combined_log {
>create
>rotate 7
>daily
>errors [EMAIL PROTECTED]
>postrotate
> /sbin/killall -HUP httpd
> analog -G +g/home/httpd/cgi-bin/company-domains.cfg
>endscript
>delaycompress
>}
> ---
>
> All I then need to do is set company-domains.cfg:
> LOGFILE /home/httpd/company-domains.net/logs/combined_log.1
>
> i.e. pointing to the rotated log file (which souldn't be compressed until
> the next rotation)? If this is right, it is a very neat solution.
>
> TIA, Brian
>
> > >Could anyone please help me build a rollover script for logfiles and
> > >analysis?? I would be happy to post the results to this list...
> > >
> > >I am on RH6.1 (intel). I have read Rebecca Minarik's script, and just
> > >need to tweak it. I am not a unix/cron expert, but neither am I stupid!
> > >I
> > > am willing to try if someone can spare a little effort with me...
> >
> > My method may be a titch simplistic, but I'm getting the results I want
> > anyway so i don't care. *g*
> >
> > I set up my analog.cfg the way I wanted... output file of index.html in
> > the /webstats directory, in my case, as well as telling analog to parse
> > /var/log/httpd/access_lo* for its data.
> >
> > I made two small edits to existing RedHat-installed files. In
> > cron.daily's logrotate script I inserted a command to run analog before
> > the actual log rotation occurs. (I did this mainly to completely avoid
> > any conceivable cross-purposes on the part of analog and the log
> > rotation scheme.) And in the logrotate.conf file I upped the weeks to 12
> > so I can have three months' worth of data in my report.
> >
> > As RedHat is already checking log rotation daily, and comes default (in
> > 6.2 anyway) setup to keep 4 weeks of rolled-over logs, there's not much
> > to it. YMMV, of course, and your goals may not be the same as mine.
> >
>
>
>
> This is the analog-help mailing list. To unsubscribe from this mailing
> list, send mail to [EMAIL PROTECTED] with "unsubscribe"
> in the main BODY OF THE MESSAGE. List archived at
> http://www.mail-archive.com/analog-help@lists.isite.net/
>
>
>
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
Re: [analog-help] log rollover and analysis
Hi Karel
Thanks for your reply - The simpler the better...OK, I think I follow
your suggestion. Below I have listed my appended contents of
/etc/cron.daily/logrotate.conf.
Could I please ask you (or anyone) to knidly check if this is alright?
One thing in particular, the '/sbin/killall -HUP httpd' command is given
as an example in the man logrotate file. Is this required??
---APPENDED TO THE BOTTOM OF LOAGROTATE.CONF---
# system-specific logs may be configured here
# Added by BC 22/5/00
/home/httpd/company-domains.net/logs/combined_log {
create
rotate 7
daily
errors [EMAIL PROTECTED]
postrotate
/sbin/killall -HUP httpd
analog -G +g/home/httpd/cgi-bin/company-domains.cfg
endscript
delaycompress
}
---
All I then need to do is set company-domains.cfg:
LOGFILE /home/httpd/company-domains.net/logs/combined_log.1
i.e. pointing to the rotated log file (which souldn't be compressed until
the next rotation)? If this is right, it is a very neat solution.
TIA, Brian
> >Could anyone please help me build a rollover script for logfiles and
> >analysis?? I would be happy to post the results to this list...
> >
> >I am on RH6.1 (intel). I have read Rebecca Minarik's script, and just
> >need to tweak it. I am not a unix/cron expert, but neither am I stupid! I
> > am willing to try if someone can spare a little effort with me...
>
> My method may be a titch simplistic, but I'm getting the results I want
> anyway so i don't care. *g*
>
> I set up my analog.cfg the way I wanted... output file of index.html in
> the /webstats directory, in my case, as well as telling analog to parse
> /var/log/httpd/access_lo* for its data.
>
> I made two small edits to existing RedHat-installed files. In cron.daily's
> logrotate script I inserted a command to run analog before the actual log
> rotation occurs. (I did this mainly to completely avoid any conceivable
> cross-purposes on the part of analog and the log rotation scheme.) And in
> the logrotate.conf file I upped the weeks to 12 so I can have three
> months' worth of data in my report.
>
> As RedHat is already checking log rotation daily, and comes default (in
> 6.2 anyway) setup to keep 4 weeks of rolled-over logs, there's not much to
> it. YMMV, of course, and your goals may not be the same as mine.
>
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
[analog-help] log rollover and analysis
Could anyone please help me build a rollover script for logfiles and
analysis?? I would be happy to post the results to this list...
I am on RH6.1 (intel). I have read Rebecca Minarik's script, and just
need to tweak it. I am not a unix/cron expert, but neither am I stupid! I
am willing to try if someone can spare a little effort with me...
I wish to set up a script (based on Rebecca's) to run analog at regular
intevals e.g. daily, weekly or monthly for a virtual domain (apache). The
script should be able to:
1] rollover the logfile to
2] create a new logfile as
3] run analog on
4] save results as
It looks like Rebecca's script will do 3] and 4]. WRT this, I have the
following questions:
A] conf_files
Am I correct in assuming this is a list of my customised conf files in
the same format as /etc/analog.cfg?? This confuses me a little as some of
the variables are already present in the .cnf file. Maybe I have this
wrong?
For multiple files the format is:
set conf_files = "site1,site2,siten"
These correspond to site1.confsiten.conf?
B] Reports
I wish to generate reports as html files. To do this:
- Can I simply remove the {set rcpts = } line and replace {set outfile =
"[existing syntax]".".html"}
- Remove the {set subj = .$rcpts < $outfile} line.
TIA for any help received...
Best regards, Brian
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/analog-help@lists.isite.net/
