how to add a superservice (was: Re: Best Development Manual)

[Hengel Zambrano]

Hi,

I followed your recomendation about use an cumulative report as it:

   2002-05-06 ................................................ 9
	a	1
	b	2
	c	3
   2002-05-07 ................................................ 0
   2002-05-08 ................................................ 0
   2002-05-09 .............................................. 188
	xxx	1
	yyy	2
	zzz	3



Now, I would like to know how can I use a "dynamic" parameter (like the ones on the cfg file). I want to use the "system date" like a parameter in order to filter just the logs for current date, I know I can filter it in
the log2dlf sybase plugin, but I want to use like a parameter because in that way I can select another dates. 

Is there any way to pass this dinamycs parameters from the command line to log2report or log2mail ??? It maybe solve my issue.


Thanks a lot again....



Hengel.




On Thu, 17 Oct 2002 13:58:59 +0200
Joost van Baal <joostvb at logreport.org> wrote:

> Hi Hengel,
> 
> [I Cc the public development at logreport.org list on my answer, the
> address developers at logreport.org is not a public list.]
> 
> On Wed, Oct 16, 2002 at 06:15:56PM -0400, Hengel Zambrano wrote:
> > Thanks for the help, 
> 
> You're welcome :)
> 
> > I made a new superservice because I want to monitor the sybase server
> > "errors". I don't want to care about queries, or log information as you
> > have at database superservice.
> 
> A, ok, that sounds like a sane thing to do.
> 
> > I would like to share the code but I have finisshed yet.
> 
> OK, we are patient :)
> 
> > Right now I have the following doubt: How can I indicate that the
> > period of the logs my service should take. I mean, if I run:
> > "lr_log2report serversybase < mylog" the report contains
> > information about ALL the log entries. I would like to filter using
> > the date, for instance from 2002/11/01 to 2002/11/02. It is because I
> > have planed to put the logreport at the crontab to
> > get daily information about my logs.
> 
> Currently, there are different ways to do this, all with their pros and
> cons.  The easiest one might be just to change your logrotating setup.
> Another one is to convert your complete logs to dlf, and split the dlf
> in chunks which should result in one report each.  A simple awk or perl
> script could take care of this: the dlf has timestamps in
> seconds-since-epoch format at fixed fields.  A third way to handle it is
> to use a filter-spec element in your report configuration file.  You can
> use the | syntax.  E.g. take a look at www/filters/select-url.xml .
> This is used in www.cfg.  There is a `gt' and a `lt' element you can use
> in a <lire:filter-spec>, these are useful when tackling your problem.
> 
> Yet another solution would be to wrap all subreports in a per-day
> timegroup: e.g. change
> 
>  top error-causing query types, by nof occerence
>   foo           12
>   bar           10
>   blah           8
> 
> into
> 
>  top error-causing query types, by nof occerence, by day
>   2002-10-11      10
>    foo             6
>    bar             4
>   2002-10-12      12
>    blah            8
>    foo             4
> 
> You'd get a cumulative report, when processing the current sybase log on
> a daily basis from cron.  You could take a look at e.g.
> email/reports/deliveries-by-period-by-status.xml for an example of a
> somewhat similar report.
> 
> > Thanks a lot again
> > 
> 
> > Bw: There is another forum or IRC channel where can I find information
> > ?.
> 
> The #logreport IRC channel on irc.freenode.net, as we state on
> http://logreport.org/contact/ .
> 
> > Because the web forum at www.logreport.org 
> 
> You are talking about our mailing list archives, I suppose?
> 
> > is very hard to use, the
> > search doesn't work well,
> 
> Indeed, when the htdig search result spans multiple pages, the next-page
> buttons are broken.  Thanks for reporting this bug.
> 
> Alternatively, one could use http://www.google.com/ and specify
> site:logreport.org along with the search terms, like e.g.
> http://www.google.com/search?q=database+superservice+site%3Alogreport.org
> 
> > neither the page buttoms.
> 
> Could you be more specific?  I just browsed through our webarchives, and
> didn't find any bug in the interface.
> 
> > I know you have made a EXCELENT work with this tool, but without
> > docummentation
> 
> I've just uploaded the current (improved and extended) documentation, in
> http://www.logreport.org/pub/cvs-snapshots/lire-1.2-20021017-cvs-DO_NOT_USE.tar.gz
> .  It's got DO_NOT_USE in its name since its untested, and very likely
> will break in many unforeseen ways.  However, the documentation which
> comes with this, like
> http://www.logreport.org/pub/cvs-snapshots/lire-1.2-20021017-cvs/doc/dev-manual/
> , is likely very useful to you.  It contains e.g.
> http://www.logreport.org/pub/cvs-snapshots/lire-1.2-20021017-cvs/doc/dev-manual/ch09.html
> on 'The Lire Report Specification Markup Language'.
> 
> > and without a good forum, list is hard to use. I wnat to
> > suggest you to host the email list at sourceforge.net that place offers
> > to you a search engine on your email list, that is pretty good.
> 
> Hm, we'd rather maintain the lists ourselves, actually.  For now, we're
> only using SourceForge for hosting our public CVS.  (We've discussed
> this issue internally.)
> 
> > But
> > again, I like the tool, just it should be good idea to make it easier to
> > use (is open source).
> 
> We've got lots of plans wrt userfriendlyness on our roadmap.
> 
> > I wait for your anwser and tell me how can I submmit my code after
> > polish and finished it.
> 
> You could upload it to a website of yours, or email it to us privately
> at logreport at logreport.org.
> 
> Bye,
> 
> Joost
> 
> -- 
> Joost van Baal              . .           http://www.logreport.org/
>                            .   .
> /^LogReport$/               . .               joostvb at logreport.org
> 
> 


-- 
Hengel Zambrano

System Administrator
NewBreak, LLC. 

Office Number: 1-203-355-1511
Optional email: hengelz at hotmail.com

-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org