perfparse-users — Problems using PerfParse

Re: [Perfparse-users] Perfparse-log2db method 2

[Yves M. <yme...@li...>]

Acknowledged. Thanks !
I'm working on Philipp Sand's changes to the install guide. Watch for my =
next answer to
him here to know where to get the updated install guide :)

Yves

> All,
>
> I tried to get "method 2" to work, as described in the install_guide fo=
und
> in the /doc directory.
> After a few hours getting nowhere, I found out a small but important de=
tail.
> The doc reads:
> <quote>
> Method 2 : Launch perfparse-log2db
> Edit misccommands.cfg and add the following :
>
> define command{
>         command_name    process-service-perfdata
>         command_line    /usr/bin/printf "%b"
> "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDAT=
A$" |
> $USER2$/bin/perfparse-log2db -c $USER2$/etc/perfparse.cfg
>         }
> </quote>
>
> Unfortunately, the 'printf' command is missing a '\n' causing pp to nev=
er
> store the line. The correct entry is:
>
> define command{
>         command_name    process-service-perfdata
>         command_line    /usr/bin/printf "%b"
> "$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDAT=
A$\n"
> | $USER2$/bin/perfparse-log2db -c $USER2$/etc/perfparse.cfg
>         }
>
> Happy perfparsing....
> Tim
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>
>


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-users] Perfparse-log2db method 2

[Tim W. <tim...@pi...>]

All,

I tried to get "method 2" to work, as described in the install_guide found
in the /doc directory.
After a few hours getting nowhere, I found out a small but important detail.
The doc reads:
<quote>
Method 2 : Launch perfparse-log2db
Edit misccommands.cfg and add the following :

define command{
        command_name    process-service-perfdata
        command_line    /usr/bin/printf "%b"
"$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$" |
$USER2$/bin/perfparse-log2db -c $USER2$/etc/perfparse.cfg
        }
</quote>

Unfortunately, the 'printf' command is missing a '\n' causing pp to never
store the line. The correct entry is:

define command{
        command_name    process-service-perfdata
        command_line    /usr/bin/printf "%b"
"$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$OUTPUT$\t$SERVICESTATE$\t$PERFDATA$\n"
| $USER2$/bin/perfparse-log2db -c $USER2$/etc/perfparse.cfg
        }

Happy perfparsing....
Tim

Re: [Perfparse-users] Perfparse binary?

[Michael T. H. <mi...@ha...>]

James,

Thanks for the info. Since posting I've found that the package-included 
docs are most recent, and the website
is somewhat out of date. Confusion cleared up!

Michael

>
> If you are using the latest version, perfparse is now called 
> perfparse-log2db (or something similar:P).  They did a major rewrite 
> and changed the name to avoid confusion because of the changes in the 
> way it works...
>
> If that isn't the solution, you should have some errors from your 
> compile job that might help to diagnose the problem ;)
>
> James
>
> -----Original Message-----
> From: Michael T. Halligan
> To: per...@li...
> Sent: 10/22/2004 5:27 PM
> Subject: [Perfparse-users] Perfparse binary?
>
> I'm currently in the process of attempting to install perfparse from
> the documentation on the website.  My latest snag is the lack of
> a perfparse binary. The documentation states that there is a binary
> which
> parses the performance data log, but this binary doesn't seem to be
> created when I make perfparse.  I'm not getting any errors during the
> compile, and I'm thinking perhaps the docs on the website are just
> rather
> oudated?
>
>
> -------------------
> BitPusher, LLC
> http://www.bitpusher.com/
> 1.888.9PUSHER
> (415) 724.7998 - Mobile
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give
> us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>


-- 
-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile

RE: [Perfparse-users] Perfparse binary?

[James O. <jo...@re...>]

 
If you are using the latest version, perfparse is now called
perfparse-log2db (or something similar:P).  They did a major rewrite and
changed the name to avoid confusion because of the changes in the way it
works...

If that isn't the solution, you should have some errors from your compile
job that might help to diagnose the problem ;)

James

-----Original Message-----
From: Michael T. Halligan
To: per...@li...
Sent: 10/22/2004 5:27 PM
Subject: [Perfparse-users] Perfparse binary?

I'm currently in the process of attempting to install perfparse from
the documentation on the website.  My latest snag is the lack of
a perfparse binary. The documentation states that there is a binary
which
parses the performance data log, but this binary doesn't seem to be
created when I make perfparse.  I'm not getting any errors during the
compile, and I'm thinking perhaps the docs on the website are just
rather
oudated?


-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give
us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Perfparse-users mailing list
Per...@li...
https://lists.sourceforge.net/lists/listinfo/perfparse-users

[Perfparse-users] Perfparse binary?

[Michael T. H. <mi...@ha...>]

I'm currently in the process of attempting to install perfparse from
the documentation on the website.  My latest snag is the lack of
a perfparse binary. The documentation states that there is a binary which
parses the performance data log, but this binary doesn't seem to be
created when I make perfparse.  I'm not getting any errors during the
compile, and I'm thinking perhaps the docs on the website are just rather
outdated?


-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile

[Perfparse-users] Perfparse binary?

[Michael T. H. <mi...@ha...>]

I'm currently in the process of attempting to install perfparse from
the documentation on the website.  My latest snag is the lack of
a perfparse binary. The documentation states that there is a binary which
parses the performance data log, but this binary doesn't seem to be
created when I make perfparse.  I'm not getting any errors during the
compile, and I'm thinking perhaps the docs on the website are just rather
oudated?


-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile

RE: [Perfparse-users] DB Size grows very fast since v101.01

[Sand P. <Phi...@sy...>]

Hi Ben,

I just checked your point with the dublicated entries. And it's just as y=
ou thought, the mechanism to remember the file location is not working he=
re. I got all the data inserted 6x.
When I run the perfparse-log2db tool without options, it seems as if it p=
arses over the whole logfile...and I already wondered why every parse las=
t so long *g*
Think I gotta write a skript, that sets the perlog to "" after each run..=
=2E

Regards,
Philipp


> -----Original Message-----
> From: Ben Clewett [mailto:Be...@cl...]=20
> Sent: Friday, October 22, 2004 12:38 PM
> To: Sand Philipp; 'per...@li...'
> Subject: Re: [Perfparse-users] DB Size grows very fast since v101.01
>=20
> Philipp,
>=20
> Lets look at the data...
>=20
> You have 3730416 rows of raw data in ~three days.  This is therefore
> ~5118 services a minute.  You say you have ~2000 metrics.  If=20
> every one of your services is posting every minute, each one=20
> having average 0.5 metrics, these figures could therefore be correct.
>=20
> If not, there is something wrong.  My first guess is that the=20
> log file is not being deleted between parses, and the=20
> mechanism to remember the file location is not working. =20
> Therefore most of your data is duplicates.  (Which are not=20
> checked for in the current version.)  Please look at the=20
> documentation, there is information in there about the two=20
> ways of deleting the log file between runs.  Also check you=20
> log, anything in it indicates some problem.
>=20
> Don't worry too much if this is the case.  When the data gets=20
> older that
>   it's deletion policy, all data and duplicates will be deleted.
>=20
> If these figures are correct, read on:
>=20
> There are ways of reducing the size, which we have to address now.
>=20
> First off, are you using both the binary (metric data) and=20
> raw (plugin output)?  If not, use of these two flags on parse:
> 	--no-raw-data
> 	--no-bin-data
>=20
> Next we have to look at your deletion policies.  The data=20
> should grow to the size of the deletion policies and no more.
>=20
> First thing to do here is to set the policy to 'Never' for=20
> any data you do not want to import.  PP will now ignore it.
>=20
> Second, decide on a limit for your data, set that limit, and=20
> ensure the perfparse-db-purge is running nightly.
>=20
> The data will now grow to a fixed size.  You know from your=20
> table below that one days data is:
>=20
> Raw:	506 / 3 =3D 167 MB / day
> Bin:	723 / 3 =3D 241 MB / day
>=20
> If, say, you don't want any raw data and you do want 30 days=20
> data for some metrics, 10 days for others, and none for the=20
> rest.  It should be easy to calculate your max. size.  Or=20
> work backwards from the space you have to see how much data=20
> you can store.
>=20
> Hope this is of some use,
>=20
> Regards
>=20
> Ben
>=20
>=20
>=20
> Sand Philipp wrote:
>=20
> > No, table space isn't define as ~3GB, it's growing=20
> constantly. Since my first mail, the database size has=20
> increased to 3,4GB...
> > Here's some Data out of the mysql database:
> > mysql> SHOW TABLE STATUS from nagios like 'perfdata_service_bin';
> > | Name                 | Type   | Row_format | Rows    |=20
> Avg_row_length | Data_length | Max_data_length | Index_length=20
> | Data_free | Auto_increment | Create_time | Update_time |=20
> Check_time | Create_options | Comment =20
> > | perfdata_service_bin | InnoDB | Dynamic    | 7005182 |   =20
>         104 |   731906048 |            NULL |   1695547392 | =20
>        0 |        6971161 | NULL        | NULL        | NULL =20
>      |                | InnoDB free: 4096 kB; (`host_name`=20
> `service_description`) REFER=20
> `nagios/perfdata_service`(`host_name` `service_description`);=20
> (`host_name` `service_description` `metric`) REFER=20
> `nagios/perfdata_service_metric`(`host_name`=20
> `service_description` `metric`) |=20
> >=20
> > So the Data lenght of the perfdata_service_bin is already=20
> at 730MB and the index size is 1.6GB ... In 3Days!
> >=20
> > Here's the output for the raw table:
> > | perfdata_service_raw | InnoDB | Dynamic    | 3730416 |   =20
>         135 |   506462208 |            NULL |    401457152 | =20
>        0 |        3611239 | NULL        | NULL        | NULL =20
>      |                | InnoDB free: 4096 kB; (`host_name`=20
> `service_description`) REFER=20
> `nagios/perfdata_service`(`host_name` `service_description`) |
> >=20
> > The serviceperf.log has only 164MB of size and hasn't been=20
> deleted since Tuesday!
> >=20
> > Regards, Philipp
> >=20
> >=20
> >>-----Original Message-----
> >>From: Ben Clewett [mailto:Be...@cl...]
> >>Sent: Friday, October 22, 2004 11:13 AM
> >>To: Sand Philipp
> >>Cc: per...@li...
> >>Subject: Re: [Perfparse-users] DB Size grows very fast since v101.01
> >>
> >>Phillipp,
> >>
> >>Nothing new added, sorry.
> >>
> >>The innodb table space is not linear.  For historical=20
> reasons it uses=20
> >>large files of a fixed size.  The size is defined in the my.cfg (I=20=

> >>believe).  My guess is that your table space size in this file is=20
> >>defined as ~3GB.  Or there is some other similar logical reason.
> >>
> >>Please check as well your log files.  These can grow faster=20
> than the=20
> >>table space.
> >>
> >>Regards, Ben.
> >>
> >>
> >>Sand Philipp wrote:
> >>
> >>
> >>>Hello,
> >>>
> >>>I created a brand new innodb Database since upgrading to
> >>
> >>101.01. In this db I insert data for ~300 hosts ~2000 metrics.=20
> >>
> >>>This Database has been created this Tuesday (10/19/2004)
> >>
> >>and it's already 3GB huge today (10/22/2004). With version 100 and=20=

> >>earlier I had a database with the same amount of hosts and=20
> metrics and=20
> >>had a Database size of about 8GB, but this had been running=20
> for a few=20
> >>months!
> >>
> >>>Had there been some fields modifications in the database?
> >>>
> >>>Regards,
> >>>Philipp
> >>>
> >>>_____________________________
> >>>
> >>>Philipp Sand
> >>>OC-CC-TEC-SYS
> >>>
> >>>SYCOR GmbH
> >>>Heinrich-von-Stephan-Stra=DFe 1-5
> >>>D - 37073 G=F6ttingen
> >>>
> >>>Telefon	+49 (0) 551 / 490 - 0
> >>>Telefax	+49 (0) 551 / 490 - 232468
> >>>
> >>>phi...@sy...
> >>>www.sycor.de
> >>>------------------------------------------------
> >>>
> >>>
> >>>
> >>>************************************************
> >>>
> >>>sycor plastics - die neue Branchenl=F6sung f=FCr die=20
> Kunststoffindustrie
> >>>
> >>>www.sycor-plastics.de
> >>>
> >>>************************************************
> >>>
> >>>
> >>>
> >>>
> >>>Diese E-Mail ist vertraulich und kann dar=FCber hinaus
> >>
> >>pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
> >>bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die E-Mai=
l und=20
> >>deren Anh=E4nge sofort und benachrichtigen Sie uns dar=FCber. Die Fir=
ma=20
> >>sycor willigt in keine Vertr=E4ge oder vertragliche=20
> Verpflichtungen ein=20
> >>oder =FCbermittelt rechtsverbindliche Angebote, die in Form=20
> von E-Mail=20
> >>versandt werden, sofern dies nicht ausdr=FCcklich in=20
> schriftlicher Form=20
> >>zwischen den Parteien vereinbart wurde.
> >>
> >>>This e-mail is confidential and may contain personal and/or
> >>
> >>privileged information. If you are not the intended=20
> recipient please=20
> >>delete this e-mail and all attachments immediately and=20
> inform us. The=20
> >>company sycor does not agree with contracts or contract obligations=20=

> >>sent by e-mail, neither do we transmit legally binding offers by=20
> >>e-mail, unless this is not expressly agreed upon between=20
> the parties=20
> >>and documented in written form.
> >>
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This SF.net email is sponsored by: IT Product Guide on=20
> >>>ITManagersJournal Use IT products in your business? Tell us
> >>
> >>what you
> >>
> >>>think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
> >>>Certificates! Click to find out more=20
> >>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >>>_______________________________________________
> >>>Perfparse-users mailing list
> >>>Per...@li...
> >>>https://lists.sourceforge.net/lists/listinfo/perfparse-users
> >>>
> >>
> >>
> >=20
> >=20
> > ************************************************
> >=20
> > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindust=
rie
> >=20
> > www.sycor-plastics.de
> >=20
> > ************************************************
> >=20
> >=20
> >=20
> >=20
> > Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20
> pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
> bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20
> E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20
> dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20
> vertragliche Verpflichtungen ein oder =FCbermittelt=20
> rechtsverbindliche Angebote, die in Form von E-Mail versandt=20
> werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20
> zwischen den Parteien vereinbart wurde.
> >=20
> > This e-mail is confidential and may contain personal and/or=20
> privileged information. If you are not the intended recipient=20
> please delete this e-mail and all attachments immediately and=20
> inform us. The company sycor does not agree with contracts or=20
> contract obligations sent by e-mail, neither do we transmit=20
> legally binding offers by e-mail, unless this is not=20
> expressly agreed upon between the parties and documented in=20
> written form.
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on=20
> > ITManagersJournal Use IT products in your business? Tell us=20
> what you=20
> > think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
> > Certificates! Click to find out more=20
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Perfparse-users mailing list
> > Per...@li...
> > https://lists.sourceforge.net/lists/listinfo/perfparse-users
> >=20
>=20
>=20


************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

Re: [Perfparse-users] DB Size grows very fast since v101.01

[Ben C. <Be...@cl...>]

Philipp,

Lets look at the data...

You have 3730416 rows of raw data in ~three days.  This is therefore=20
~5118 services a minute.  You say you have ~2000 metrics.  If every one=20
of your services is posting every minute, each one having average 0.5=20
metrics, these figures could therefore be correct.

If not, there is something wrong.  My first guess is that the log file=20
is not being deleted between parses, and the mechanism to remember the=20
file location is not working.  Therefore most of your data is=20
duplicates.  (Which are not checked for in the current version.)  Please=20
look at the documentation, there is information in there about the two=20
ways of deleting the log file between runs.  Also check you log,=20
anything in it indicates some problem.

Don't worry too much if this is the case.  When the data gets older that=20
  it's deletion policy, all data and duplicates will be deleted.

If these figures are correct, read on:

There are ways of reducing the size, which we have to address now.

First off, are you using both the binary (metric data) and raw (plugin=20
output)?  If not, use of these two flags on parse:
	--no-raw-data
	--no-bin-data

Next we have to look at your deletion policies.  The data should grow to=20
the size of the deletion policies and no more.

First thing to do here is to set the policy to 'Never' for any data you=20
do not want to import.  PP will now ignore it.

Second, decide on a limit for your data, set that limit, and ensure the=20
perfparse-db-purge is running nightly.

The data will now grow to a fixed size.  You know from your table below=20
that one days data is:

Raw:	506 / 3 =3D 167 MB / day
Bin:	723 / 3 =3D 241 MB / day

If, say, you don't want any raw data and you do want 30 days data for=20
some metrics, 10 days for others, and none for the rest.  It should be=20
easy to calculate your max. size.  Or work backwards from the space you=20
have to see how much data you can store.

Hope this is of some use,

Regards

Ben



Sand Philipp wrote:

> No, table space isn't define as ~3GB, it's growing constantly. Since my=
 first mail, the database size has increased to 3,4GB...
> Here's some Data out of the mysql database:
> mysql> SHOW TABLE STATUS from nagios like 'perfdata_service_bin';
> | Name                 | Type   | Row_format | Rows    | Avg_row_length=
 | Data_length | Max_data_length | Index_length | Data_free | Auto_increm=
ent | Create_time | Update_time | Check_time | Create_options | Comment =20
> | perfdata_service_bin | InnoDB | Dynamic    | 7005182 |            104=
 |   731906048 |            NULL |   1695547392 |         0 |        6971=
161 | NULL        | NULL        | NULL       |                | InnoDB fr=
ee: 4096 kB; (`host_name` `service_description`) REFER `nagios/perfdata_s=
ervice`(`host_name` `service_description`); (`host_name` `service_descrip=
tion` `metric`) REFER `nagios/perfdata_service_metric`(`host_name` `servi=
ce_description` `metric`) |=20
>=20
> So the Data lenght of the perfdata_service_bin is already at 730MB and =
the index size is 1.6GB ... In 3Days!
>=20
> Here's the output for the raw table:
> | perfdata_service_raw | InnoDB | Dynamic    | 3730416 |            135=
 |   506462208 |            NULL |    401457152 |         0 |        3611=
239 | NULL        | NULL        | NULL       |                | InnoDB fr=
ee: 4096 kB; (`host_name` `service_description`) REFER `nagios/perfdata_s=
ervice`(`host_name` `service_description`) |
>=20
> The serviceperf.log has only 164MB of size and hasn't been deleted sinc=
e Tuesday!
>=20
> Regards, Philipp
>=20
>=20
>>-----Original Message-----
>>From: Ben Clewett [mailto:Be...@cl...]=20
>>Sent: Friday, October 22, 2004 11:13 AM
>>To: Sand Philipp
>>Cc: per...@li...
>>Subject: Re: [Perfparse-users] DB Size grows very fast since v101.01
>>
>>Phillipp,
>>
>>Nothing new added, sorry.
>>
>>The innodb table space is not linear.  For historical reasons=20
>>it uses large files of a fixed size.  The size is defined in=20
>>the my.cfg (I believe).  My guess is that your table space=20
>>size in this file is defined as ~3GB.  Or there is some other=20
>>similar logical reason.
>>
>>Please check as well your log files.  These can grow faster=20
>>than the table space.
>>
>>Regards, Ben.
>>
>>
>>Sand Philipp wrote:
>>
>>
>>>Hello,
>>>
>>>I created a brand new innodb Database since upgrading to=20
>>
>>101.01. In this db I insert data for ~300 hosts ~2000 metrics.=20
>>
>>>This Database has been created this Tuesday (10/19/2004)=20
>>
>>and it's already 3GB huge today (10/22/2004). With version=20
>>100 and earlier I had a database with the same amount of=20
>>hosts and metrics and had a Database size of about 8GB, but=20
>>this had been running for a few months!
>>
>>>Had there been some fields modifications in the database?
>>>
>>>Regards,
>>>Philipp
>>>
>>>_____________________________
>>>
>>>Philipp Sand
>>>OC-CC-TEC-SYS
>>>
>>>SYCOR GmbH
>>>Heinrich-von-Stephan-Stra=DFe 1-5
>>>D - 37073 G=F6ttingen
>>>
>>>Telefon	+49 (0) 551 / 490 - 0
>>>Telefax	+49 (0) 551 / 490 - 232468
>>>
>>>phi...@sy...
>>>www.sycor.de
>>>------------------------------------------------
>>>
>>>
>>>
>>>************************************************
>>>
>>>sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustr=
ie
>>>
>>>www.sycor-plastics.de
>>>
>>>************************************************
>>>
>>>
>>>
>>>
>>>Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20
>>
>>pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
>>bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20
>>E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20
>>dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20
>>vertragliche Verpflichtungen ein oder =FCbermittelt=20
>>rechtsverbindliche Angebote, die in Form von E-Mail versandt=20
>>werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20
>>zwischen den Parteien vereinbart wurde.
>>
>>>This e-mail is confidential and may contain personal and/or=20
>>
>>privileged information. If you are not the intended recipient=20
>>please delete this e-mail and all attachments immediately and=20
>>inform us. The company sycor does not agree with contracts or=20
>>contract obligations sent by e-mail, neither do we transmit=20
>>legally binding offers by e-mail, unless this is not=20
>>expressly agreed upon between the parties and documented in=20
>>written form.
>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: IT Product Guide on=20
>>>ITManagersJournal Use IT products in your business? Tell us=20
>>
>>what you=20
>>
>>>think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
>>>Certificates! Click to find out more=20
>>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>>_______________________________________________
>>>Perfparse-users mailing list
>>>Per...@li...
>>>https://lists.sourceforge.net/lists/listinfo/perfparse-users
>>>
>>
>>
>=20
>=20
> ************************************************
>=20
> sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri=
e
>=20
> www.sycor-plastics.de
>=20
> ************************************************
>=20
>=20
>=20
>=20
> Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In=
formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n=
ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b=
enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.
>=20
> This e-mail is confidential and may contain personal and/or privileged =
information. If you are not the intended recipient please delete this e-m=
ail and all attachments immediately and inform us. The company sycor does=
 not agree with contracts or contract obligations sent by e-mail, neither=
 do we transmit legally binding offers by e-mail, unless this is not expr=
essly agreed upon between the parties and documented in written form.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

RE: [Perfparse-users] DB Size grows very fast since v101.01

[Sand P. <Phi...@sy...>]

No, table space isn't define as ~3GB, it's growing constantly. Since my f=
irst mail, the database size has increased to 3,4GB...
Here's some Data out of the mysql database:
mysql> SHOW TABLE STATUS from nagios like 'perfdata_service_bin';
| Name                 | Type   | Row_format | Rows    | Avg_row_length |=
 Data_length | Max_data_length | Index_length | Data_free | Auto_incremen=
t | Create_time | Update_time | Check_time | Create_options | Comment =20=

| perfdata_service_bin | InnoDB | Dynamic    | 7005182 |            104 |=
   731906048 |            NULL |   1695547392 |         0 |        697116=
1 | NULL        | NULL        | NULL       |                | InnoDB free=
: 4096 kB; (`host_name` `service_description`) REFER `nagios/perfdata_ser=
vice`(`host_name` `service_description`); (`host_name` `service_descripti=
on` `metric`) REFER `nagios/perfdata_service_metric`(`host_name` `service=
_description` `metric`) |=20

So the Data lenght of the perfdata_service_bin is already at 730MB and th=
e index size is 1.6GB ... In 3Days!

Here's the output for the raw table:
| perfdata_service_raw | InnoDB | Dynamic    | 3730416 |            135 |=
   506462208 |            NULL |    401457152 |         0 |        361123=
9 | NULL        | NULL        | NULL       |                | InnoDB free=
: 4096 kB; (`host_name` `service_description`) REFER `nagios/perfdata_ser=
vice`(`host_name` `service_description`) |

The serviceperf.log has only 164MB of size and hasn't been deleted since =
Tuesday!

Regards, Philipp

> -----Original Message-----
> From: Ben Clewett [mailto:Be...@cl...]=20
> Sent: Friday, October 22, 2004 11:13 AM
> To: Sand Philipp
> Cc: per...@li...
> Subject: Re: [Perfparse-users] DB Size grows very fast since v101.01
>=20
> Phillipp,
>=20
> Nothing new added, sorry.
>=20
> The innodb table space is not linear.  For historical reasons=20
> it uses large files of a fixed size.  The size is defined in=20
> the my.cfg (I believe).  My guess is that your table space=20
> size in this file is defined as ~3GB.  Or there is some other=20
> similar logical reason.
>=20
> Please check as well your log files.  These can grow faster=20
> than the table space.
>=20
> Regards, Ben.
>=20
>=20
> Sand Philipp wrote:
>=20
> > Hello,
> >=20
> > I created a brand new innodb Database since upgrading to=20
> 101.01. In this db I insert data for ~300 hosts ~2000 metrics.=20
> > This Database has been created this Tuesday (10/19/2004)=20
> and it's already 3GB huge today (10/22/2004). With version=20
> 100 and earlier I had a database with the same amount of=20
> hosts and metrics and had a Database size of about 8GB, but=20
> this had been running for a few months!
> > Had there been some fields modifications in the database?
> >=20
> > Regards,
> > Philipp
> >=20
> > _____________________________
> >=20
> > Philipp Sand
> > OC-CC-TEC-SYS
> >=20
> > SYCOR GmbH
> > Heinrich-von-Stephan-Stra=DFe 1-5
> > D - 37073 G=F6ttingen
> >=20
> > Telefon	+49 (0) 551 / 490 - 0
> > Telefax	+49 (0) 551 / 490 - 232468
> >=20
> > phi...@sy...
> > www.sycor.de
> > ------------------------------------------------
> >=20
> >=20
> >=20
> > ************************************************
> >=20
> > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindust=
rie
> >=20
> > www.sycor-plastics.de
> >=20
> > ************************************************
> >=20
> >=20
> >=20
> >=20
> > Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20
> pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
> bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20
> E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20
> dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20
> vertragliche Verpflichtungen ein oder =FCbermittelt=20
> rechtsverbindliche Angebote, die in Form von E-Mail versandt=20
> werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20
> zwischen den Parteien vereinbart wurde.
> >=20
> > This e-mail is confidential and may contain personal and/or=20
> privileged information. If you are not the intended recipient=20
> please delete this e-mail and all attachments immediately and=20
> inform us. The company sycor does not agree with contracts or=20
> contract obligations sent by e-mail, neither do we transmit=20
> legally binding offers by e-mail, unless this is not=20
> expressly agreed upon between the parties and documented in=20
> written form.
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on=20
> > ITManagersJournal Use IT products in your business? Tell us=20
> what you=20
> > think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
> > Certificates! Click to find out more=20
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Perfparse-users mailing list
> > Per...@li...
> > https://lists.sourceforge.net/lists/listinfo/perfparse-users
> >=20
>=20
>=20


************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

Re: [Perfparse-users] DB Size grows very fast since v101.01

[Yves M. <yme...@li...>]

> Phillipp,
>
> Nothing new added, sorry.

Well, yes, a minor change.
perfdata_state is no more used
perfdata_registry should contain something like 7 lines per host running =
perfparse,
instead of 5 with older version (8 instead of 6 under Linux).
And there should be an additionnal line pp/database/version.

So you should have 2 more lines per host plus one.

For one solaris host, I have 8 lines.

This is the only change.

Yves

--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

Re: [Perfparse-users] DB Size grows very fast since v101.01

[Ben C. <Be...@cl...>]

Phillipp,

Nothing new added, sorry.

The innodb table space is not linear.  For historical reasons it uses=20
large files of a fixed size.  The size is defined in the my.cfg (I=20
believe).  My guess is that your table space size in this file is=20
defined as ~3GB.  Or there is some other similar logical reason.

Please check as well your log files.  These can grow faster than the=20
table space.

Regards, Ben.


Sand Philipp wrote:

> Hello,
>=20
> I created a brand new innodb Database since upgrading to 101.01. In thi=
s db I insert data for ~300 hosts ~2000 metrics.=20
> This Database has been created this Tuesday (10/19/2004) and it's alrea=
dy 3GB huge today (10/22/2004). With version 100 and earlier I had a data=
base with the same amount of hosts and metrics and had a Database size of=
 about 8GB, but this had been running for a few months!
> Had there been some fields modifications in the database?
>=20
> Regards,
> Philipp
>=20
> _____________________________
>=20
> Philipp Sand
> OC-CC-TEC-SYS
>=20
> SYCOR GmbH
> Heinrich-von-Stephan-Stra=DFe 1-5
> D - 37073 G=F6ttingen
>=20
> Telefon	+49 (0) 551 / 490 - 0
> Telefax	+49 (0) 551 / 490 - 232468
>=20
> phi...@sy...
> www.sycor.de
> ------------------------------------------------
>=20
>=20
>=20
> ************************************************
>=20
> sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri=
e
>=20
> www.sycor-plastics.de
>=20
> ************************************************
>=20
>=20
>=20
>=20
> Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In=
formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n=
ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b=
enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.
>=20
> This e-mail is confidential and may contain personal and/or privileged =
information. If you are not the intended recipient please delete this e-m=
ail and all attachments immediately and inform us. The company sycor does=
 not agree with contracts or contract obligations sent by e-mail, neither=
 do we transmit legally binding offers by e-mail, unless this is not expr=
essly agreed upon between the parties and documented in written form.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

[Perfparse-users] DB Size grows very fast since v101.01

[Sand P. <Phi...@sy...>]

Hello,

I created a brand new innodb Database since upgrading to 101.01. In this =
db I insert data for ~300 hosts ~2000 metrics.=20
This Database has been created this Tuesday (10/19/2004) and it's already=
 3GB huge today (10/22/2004). With version 100 and earlier I had a databa=
se with the same amount of hosts and metrics and had a Database size of a=
bout 8GB, but this had been running for a few months!
Had there been some fields modifications in the database?

Regards,
Philipp

_____________________________

Philipp Sand
OC-CC-TEC-SYS

SYCOR GmbH
Heinrich-von-Stephan-Stra=DFe 1-5
D - 37073 G=F6ttingen

Telefon	+49 (0) 551 / 490 - 0
Telefax	+49 (0) 551 / 490 - 232468

phi...@sy...
www.sycor.de
------------------------------------------------



************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

Re: [Perfparse-users] Problem compiling on RHEL3 with MySQL 4.0.21

[Yves M. <yme...@li...>]

You are using glib-1.2.
If you can, use glib-2

Otherwise, edit libpp_mysql/db_macro_actions.c around line 126 :

char *db_version_error() {
  char *sstr; /* add this line */
  GString *s =3D NULL;
  ...

  /* return g_string_free(s, FALSE); */
  sstr =3D s->str;
  g_string_free(s, FALSE);
  return(sstr);
}

The problem is a change in GLib API.
In glib-1.2 we have
void g_string_free(...)
In glib-2, we have
gchar *g_string_free(...)

The compiler complains about that.

This will be OK for version 0.102.1 that should be released soon.

Yves

> My setup is :
>
> nagios 1.2
> RHEL 3 WS (fully up to date)
> MySQL 4.0.21 (rpms from mysql.com)
> perfparse-0.101.1
>
> The problem I'm getting is during compilation of perfparse, make errors
> out with this :
>
>
>
>
> make  all-recursive
> make[1]: Entering directory `/home/nagios_software/build/perfparse-0.10=
1.1'
> Making all in libpp_common
> make[2]: Entering directory
> `/home/nagios_software/build/perfparse-0.101.1/libpp_common'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/nagios_software/build/perfparse-0.101.1/libpp_common'
> Making all in libpp_mysql
> make[2]: Entering directory
> `/home/nagios_software/build/perfparse-0.101.1/libpp_mysql'
> if /bin/sh ../libtool --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -I. -I..
> -I/usr/include/mysql -mcpu=3Di486 -fno-strength-reduce
> -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I../libpp_common
> '-DSYSCONFDIR=3D"/home/nagios/etc"' '-DPREFIX=3D"/home/nagios"'   -g -O=
2 -Wall
> -MT libpp_mysql_la-db_macro_actions.lo -MD -MP -MF
> ".deps/libpp_mysql_la-db_macro_actions.Tpo" -c -o
> libpp_mysql_la-db_macro_actions.lo `test -f 'db_macro_actions.c' || ech=
o
> './'`db_macro_actions.c; \
> then mv -f ".deps/libpp_mysql_la-db_macro_actions.Tpo"
> ".deps/libpp_mysql_la-db_macro_actions.Plo"; else rm -f
> ".deps/libpp_mysql_la-db_macro_actions.Tpo"; exit 1; fi
>  gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/mysql -mcpu=3Di486
> -fno-strength-reduce -I/usr/include/glib-1.2 -I/usr/lib/glib/include
> -I../libpp_common -DSYSCONFDIR=3D\"/home/nagios/etc\"
> -DPREFIX=3D\"/home/nagios\" -g -O2 -Wall -MT
> libpp_mysql_la-db_macro_actions.lo -MD -MP -MF
> .deps/libpp_mysql_la-db_macro_actions.Tpo -c db_macro_actions.c  -fPIC
> -DPIC -o .libs/libpp_mysql_la-db_macro_actions.o
> db_macro_actions.c: In function `db_version_error':
> db_macro_actions.c:126: void value not ignored as it ought to be
> make[2]: *** [libpp_mysql_la-db_macro_actions.lo] Error 1
> make[2]: Leaving directory
> `/home/nagios_software/build/perfparse-0.101.1/libpp_mysql'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/nagios_software/build/perfparse-0.101=
.1'
> make: *** [all] Error 2
>
> -------------------
> BitPusher, LLC
> http://www.bitpusher.com/
> 1.888.9PUSHER
> (415) 724.7998 - Mobile
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>
>


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-users] Problem compiling on RHEL3 with MySQL 4.0.21

[Michael T. H. <mi...@ha...>]

My setup is :

nagios 1.2
RHEL 3 WS (fully up to date)
MySQL 4.0.21 (rpms from mysql.com)
perfparse-0.101.1

The problem I'm getting is during compilation of perfparse, make errors
out with this :




make  all-recursive
make[1]: Entering directory `/home/nagios_software/build/perfparse-0.101.=
1'
Making all in libpp_common
make[2]: Entering directory
`/home/nagios_software/build/perfparse-0.101.1/libpp_common'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/nagios_software/build/perfparse-0.101.1/libpp_common'
Making all in libpp_mysql
make[2]: Entering directory
`/home/nagios_software/build/perfparse-0.101.1/libpp_mysql'
if /bin/sh ../libtool --mode=3Dcompile gcc -DHAVE_CONFIG_H -I. -I. -I..
-I/usr/include/mysql -mcpu=3Di486 -fno-strength-reduce=20
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I../libpp_common
'-DSYSCONFDIR=3D"/home/nagios/etc"' '-DPREFIX=3D"/home/nagios"'   -g -O2 =
-Wall
-MT libpp_mysql_la-db_macro_actions.lo -MD -MP -MF
".deps/libpp_mysql_la-db_macro_actions.Tpo" -c -o
libpp_mysql_la-db_macro_actions.lo `test -f 'db_macro_actions.c' || echo
'./'`db_macro_actions.c; \
then mv -f ".deps/libpp_mysql_la-db_macro_actions.Tpo"
".deps/libpp_mysql_la-db_macro_actions.Plo"; else rm -f
".deps/libpp_mysql_la-db_macro_actions.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/mysql -mcpu=3Di486
-fno-strength-reduce -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I../libpp_common -DSYSCONFDIR=3D\"/home/nagios/etc\"
-DPREFIX=3D\"/home/nagios\" -g -O2 -Wall -MT
libpp_mysql_la-db_macro_actions.lo -MD -MP -MF
.deps/libpp_mysql_la-db_macro_actions.Tpo -c db_macro_actions.c  -fPIC
-DPIC -o .libs/libpp_mysql_la-db_macro_actions.o
db_macro_actions.c: In function `db_version_error':
db_macro_actions.c:126: void value not ignored as it ought to be
make[2]: *** [libpp_mysql_la-db_macro_actions.lo] Error 1
make[2]: Leaving directory
`/home/nagios_software/build/perfparse-0.101.1/libpp_mysql'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/nagios_software/build/perfparse-0.101.1=
'
make: *** [all] Error 2

-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile

Re: [Perfparse-users] 0.101.1 Statistics under Graph??

[Ben C. <Be...@cl...>]

Sand Philipp wrote:

> I'm interested in it :)
> Maybe there would be a chance to include one check box for that in the =
line where you can also select to draw a smooth graph, which is unchecked=
 by default. Ppl who wanne have those stats have to wait a little bit lon=
ger than, but it would be nice to have such an option. Especially when yo=
u make queries over an large timescale, it's nice to have those avg, min =
and max values, to post it to the customer.

I'll have to think about the check-box as this might not work with some=20
users.  I am sure there is an elegant way of getting the stats.

In the mean while, the hack to the code is simple.  Find the file=20
cgi_graph.c and edit.

Near the top, add the line:

#define SHOW_STATS

Edit the file perfchart.c and again near the top, add the above line.

make install and let me know if it works.  But please disable use of=20
http proxy for users wanting to see PP :)

Regards,

Ben


>=20
> Thanks,
> Philipp
>=20
>=20
>>-----Original Message-----
>>From: Ben Clewett [mailto:Be...@cl...]=20
>>Sent: Tuesday, October 19, 2004 5:19 PM
>>To: Sand Philipp
>>Cc: per...@li...
>>Subject: Re: [Perfparse-users] 0.101.1 Statistics under Graph??
>>
>>Sand Philipp wrote:
>>
>>
>>>Hi,
>>>
>>>I just draw a few graphs with the new Version and was=20
>>
>>pretty "shocked" that the hole Statistics Part under the=20
>>Graph are missing! Why did you remove that feature?
>>
>>>Would be great to have it back in 0.101.2 :-)
>>
>>Hi Philipp,
>>
>>I am sorry about that.  The stats were originally calculated=20
>>separately.=20
>>  This meant the graphs were slow, two reads of the database.=20
>> So I got them to calculate once and store in an external=20
>>file, at the same time as getting the data.  Written by the=20
>>image program (perfchart.cgi), read by the HTML frame to the=20
>>graph (perfgraph.cgi) and displayed.
>>
>>I used a 'hack', by half showing the HTML including the URL=20
>>to the image.  The image program would run.  Then the rest of=20
>>the HTML would show including the stats :)  Which I found out=20
>>later didn't work using a Proxy, as this fully assembles the=20
>>HTML before sending to client browser.  This caused long=20
>>timeouts and strange errors, which I never got a good fix to.
>>
>>The only neat solution is to get the graph calling HTML to=20
>>assemble all the data in a tmp file, get the stats, then call=20
>>the graph to read the tmp file and display.  Which was also=20
>>going to form the start of a cache to speed up graph drawing=20
>>by several orders.  But not got there yet :)
>>
>>These will return at a later date.  If you are not using PP=20
>>through a proxy server, it's easy to get the stats back. =20
>>I'll email you some instructions if you want.
>>
>>Regards, Ben.
>>
>>
>>
>>
>>
>>>Regards,
>>>Philipp
>>>
>>>
>>>
>>>_____________________________
>>>
>>>Philipp Sand
>>>OC-CC-TEC-SYS
>>>
>>>SYCOR GmbH
>>>Heinrich-von-Stephan-Stra=DFe 1-5
>>>D - 37073 G=F6ttingen
>>>
>>>Telefon	+49 (0) 551 / 490 - 0
>>>Telefax	+49 (0) 551 / 490 - 232468
>>>
>>>phi...@sy...
>>>www.sycor.de
>>>------------------------------------------------
>>>
>>>
>>>
>>>************************************************
>>>
>>>sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustr=
ie
>>>
>>>www.sycor-plastics.de
>>>
>>>************************************************
>>>
>>>
>>>
>>>
>>>Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20
>>
>>pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
>>bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20
>>E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20
>>dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20
>>vertragliche Verpflichtungen ein oder =FCbermittelt=20
>>rechtsverbindliche Angebote, die in Form von E-Mail versandt=20
>>werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20
>>zwischen den Parteien vereinbart wurde.
>>
>>>This e-mail is confidential and may contain personal and/or=20
>>
>>privileged information. If you are not the intended recipient=20
>>please delete this e-mail and all attachments immediately and=20
>>inform us. The company sycor does not agree with contracts or=20
>>contract obligations sent by e-mail, neither do we transmit=20
>>legally binding offers by e-mail, unless this is not=20
>>expressly agreed upon between the parties and documented in=20
>>written form.
>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: IT Product Guide on=20
>>>ITManagersJournal Use IT products in your business? Tell us=20
>>
>>what you=20
>>
>>>think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
>>>Certificates! Click to find out more=20
>>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>>_______________________________________________
>>>Perfparse-users mailing list
>>>Per...@li...
>>>https://lists.sourceforge.net/lists/listinfo/perfparse-users
>>>
>>
>>
>=20
>=20
> ************************************************
>=20
> sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri=
e
>=20
> www.sycor-plastics.de
>=20
> ************************************************
>=20
>=20
>=20
>=20
> Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In=
formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n=
ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b=
enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.
>=20
> This e-mail is confidential and may contain personal and/or privileged =
information. If you are not the intended recipient please delete this e-m=
ail and all attachments immediately and inform us. The company sycor does=
 not agree with contracts or contract obligations sent by e-mail, neither=
 do we transmit legally binding offers by e-mail, unless this is not expr=
essly agreed upon between the parties and documented in written form.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

Re: [Perfparse-users] Error link on main page Perfparse version 0.101.1

[Ben C. <Be...@cl...>]

Bertinelli Massimo wrote:

> Someone have problem with link on main page of perfparse:
> 
> Graph Binary Data. 
> <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?select_host=1>


> Http server return 500 error and the log says:
> 
> malformed header from pergraph.cgi.

This is likely to mean the CGI programs crashed.  Possibly during 
connection to the MySQL database.  Which is not done on the menu page, 
but in all sub-options.

Can you please check the following, which you may email to me if you wish:

- Check your build configuration options.  There is a sample 
configuration shown in the documentation.  Look specifically for the 
location of the configuration file, which is used by the CGI from this 
definition.

- Check your client version of MySQL.  Ensure this is exactly the same 
as the version of the SQL Server you are using.

- Check the database option in the perfparse.cfg configuration file.

I hope one of these options shows where the error is located.

Regards, Ben.

[Perfparse-users] Error link on main page Perfparse version 0.101.1

[Bertinelli M. <Ber...@an...>]

Someone have problem with link on main page of perfparse:


 


 

Graph Binary <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?select_host=1>
Data. 


 

View and Graph <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?all_bin=1>
Binary Data. 


 

View Raw Plugin <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?all_raw=1>
Data.


 

View Stored <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?saved_graphs=1>
Graphs.


 


 


 

View <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?add_amend_host_group=1>
/ Edit Host Groups 


 

View / <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?edit_host_list=1>
Edit Host Groups List. 


 

 


 

View <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?edit_delete_policies=1>
/ Edit Deletion Policy Templates 


 

View
<http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?edit_host_delete_policies=1>
/ Edit Hosts Deletion Policy. 


 

View <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?delete_policy_bin=1>  /
Edit Binary Data Deletion Policy. 


 

View <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?delete_policy_raw=1>  /
Edit Raw Data Deletion Policy. 


 

 


 

Mark <http://gsrlinux/nagios12/cgi-bin/perfgraph.cgi?mark_for_deletion=1>
hosts for complete data deletion

 

Http server return 500 error and the log says:

malformed header from pergraph.cgi.

 

All link don't work ,and compile and install the new release same the first.

Thanks for help

Reguards Massimo.

 

 

 

			

 

RE: [Perfparse-users] 0.101.1 Statistics under Graph??

[Sand P. <Phi...@sy...>]

I'm interested in it :)
Maybe there would be a chance to include one check box for that in the li=
ne where you can also select to draw a smooth graph, which is unchecked b=
y default. Ppl who wanne have those stats have to wait a little bit longe=
r than, but it would be nice to have such an option. Especially when you =
make queries over an large timescale, it's nice to have those avg, min an=
d max values, to post it to the customer.

Thanks,
Philipp

> -----Original Message-----
> From: Ben Clewett [mailto:Be...@cl...]=20
> Sent: Tuesday, October 19, 2004 5:19 PM
> To: Sand Philipp
> Cc: per...@li...
> Subject: Re: [Perfparse-users] 0.101.1 Statistics under Graph??
>=20
> Sand Philipp wrote:
>=20
> > Hi,
> >=20
> > I just draw a few graphs with the new Version and was=20
> pretty "shocked" that the hole Statistics Part under the=20
> Graph are missing! Why did you remove that feature?
> > Would be great to have it back in 0.101.2 :-)
>=20
> Hi Philipp,
>=20
> I am sorry about that.  The stats were originally calculated=20
> separately.=20
>   This meant the graphs were slow, two reads of the database.=20
>  So I got them to calculate once and store in an external=20
> file, at the same time as getting the data.  Written by the=20
> image program (perfchart.cgi), read by the HTML frame to the=20
> graph (perfgraph.cgi) and displayed.
>=20
> I used a 'hack', by half showing the HTML including the URL=20
> to the image.  The image program would run.  Then the rest of=20
> the HTML would show including the stats :)  Which I found out=20
> later didn't work using a Proxy, as this fully assembles the=20
> HTML before sending to client browser.  This caused long=20
> timeouts and strange errors, which I never got a good fix to.
>=20
> The only neat solution is to get the graph calling HTML to=20
> assemble all the data in a tmp file, get the stats, then call=20
> the graph to read the tmp file and display.  Which was also=20
> going to form the start of a cache to speed up graph drawing=20
> by several orders.  But not got there yet :)
>=20
> These will return at a later date.  If you are not using PP=20
> through a proxy server, it's easy to get the stats back. =20
> I'll email you some instructions if you want.
>=20
> Regards, Ben.
>=20
>=20
>=20
>=20
> >=20
> > Regards,
> > Philipp
> >=20
> >=20
> >=20
> > _____________________________
> >=20
> > Philipp Sand
> > OC-CC-TEC-SYS
> >=20
> > SYCOR GmbH
> > Heinrich-von-Stephan-Stra=DFe 1-5
> > D - 37073 G=F6ttingen
> >=20
> > Telefon	+49 (0) 551 / 490 - 0
> > Telefax	+49 (0) 551 / 490 - 232468
> >=20
> > phi...@sy...
> > www.sycor.de
> > ------------------------------------------------
> >=20
> >=20
> >=20
> > ************************************************
> >=20
> > sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindust=
rie
> >=20
> > www.sycor-plastics.de
> >=20
> > ************************************************
> >=20
> >=20
> >=20
> >=20
> > Diese E-Mail ist vertraulich und kann dar=FCber hinaus=20
> pers=F6nliche Informationen beinhalten. Wenn Sie nicht der=20
> bestimmungsgem=E4=DFe Empf=E4nger sind, l=F6schen Sie bitte die=20
> E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns=20
> dar=FCber. Die Firma sycor willigt in keine Vertr=E4ge oder=20
> vertragliche Verpflichtungen ein oder =FCbermittelt=20
> rechtsverbindliche Angebote, die in Form von E-Mail versandt=20
> werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form=20
> zwischen den Parteien vereinbart wurde.
> >=20
> > This e-mail is confidential and may contain personal and/or=20
> privileged information. If you are not the intended recipient=20
> please delete this e-mail and all attachments immediately and=20
> inform us. The company sycor does not agree with contracts or=20
> contract obligations sent by e-mail, neither do we transmit=20
> legally binding offers by e-mail, unless this is not=20
> expressly agreed upon between the parties and documented in=20
> written form.
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on=20
> > ITManagersJournal Use IT products in your business? Tell us=20
> what you=20
> > think of them. Give us Your Opinions, Get Free ThinkGeek Gift=20
> > Certificates! Click to find out more=20
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Perfparse-users mailing list
> > Per...@li...
> > https://lists.sourceforge.net/lists/listinfo/perfparse-users
> >=20
>=20
>=20


************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

Re: [Perfparse-users] 0.101.1 Statistics under Graph??

[Ben C. <Be...@cl...>]

Sand Philipp wrote:

> Hi,
>=20
> I just draw a few graphs with the new Version and was pretty "shocked" =
that the hole Statistics Part under the Graph are missing! Why did you re=
move that feature?
> Would be great to have it back in 0.101.2 :-)

Hi Philipp,

I am sorry about that.  The stats were originally calculated separately.=20
  This meant the graphs were slow, two reads of the database.  So I got=20
them to calculate once and store in an external file, at the same time=20
as getting the data.  Written by the image program (perfchart.cgi), read=20
by the HTML frame to the graph (perfgraph.cgi) and displayed.

I used a 'hack', by half showing the HTML including the URL to the=20
image.  The image program would run.  Then the rest of the HTML would=20
show including the stats :)  Which I found out later didn't work using a=20
Proxy, as this fully assembles the HTML before sending to client=20
browser.  This caused long timeouts and strange errors, which I never=20
got a good fix to.

The only neat solution is to get the graph calling HTML to assemble all=20
the data in a tmp file, get the stats, then call the graph to read the=20
tmp file and display.  Which was also going to form the start of a cache=20
to speed up graph drawing by several orders.  But not got there yet :)

These will return at a later date.  If you are not using PP through a=20
proxy server, it's easy to get the stats back.  I'll email you some=20
instructions if you want.

Regards, Ben.




>=20
> Regards,
> Philipp
>=20
>=20
>=20
> _____________________________
>=20
> Philipp Sand
> OC-CC-TEC-SYS
>=20
> SYCOR GmbH
> Heinrich-von-Stephan-Stra=DFe 1-5
> D - 37073 G=F6ttingen
>=20
> Telefon	+49 (0) 551 / 490 - 0
> Telefax	+49 (0) 551 / 490 - 232468
>=20
> phi...@sy...
> www.sycor.de
> ------------------------------------------------
>=20
>=20
>=20
> ************************************************
>=20
> sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustri=
e
>=20
> www.sycor-plastics.de
>=20
> ************************************************
>=20
>=20
>=20
>=20
> Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche In=
formationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4n=
ger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und b=
enachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.
>=20
> This e-mail is confidential and may contain personal and/or privileged =
information. If you are not the intended recipient please delete this e-m=
ail and all attachments immediately and inform us. The company sycor does=
 not agree with contracts or contract obligations sent by e-mail, neither=
 do we transmit legally binding offers by e-mail, unless this is not expr=
essly agreed upon between the parties and documented in written form.
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJourna=
l
> Use IT products in your business? Tell us what you think of them. Give =
us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>=20

Re: RES: [Perfparse-users] Warning/critical values not going into the database... Again

[Yves M. <yme...@li...>]

Hi Paulo,

I'm the author of most code of perfparse-log2db so I pay a lot of attenti=
on to your
emails even if Ben answers faster than me.
I will add some things to Ben's answer...

> I've found that perfparse has now the infrastructure to use ranges of w=
arning/critical
> data, and the problem is that the database hasn't changed in order to u=
se these values
> (as far as I can see, at least).
>
> Part of the problem is at save_bin_data at storage_mysql.c:
>
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_WARN_START]));
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_CRIT_START]));
>         g_string_append_printf(s_SQL, ", %s)",
>                 getSafeD(perf->metric_state));
>
> I've changed it to
>
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_WARN_END]));
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_CRIT_END]));
>         g_string_append_printf(s_SQL, ", %s)",
>                 getSafeD(perf->metric_state));
>

This is fixed for the 0.102 branch I'm working on. Ben will decide to rel=
ease 0.101.2
with that or to wait for other fixes.

> and the data begun to show up in perfdata_service_bin. However, metric_=
state values were
> still wrong and inconsistent indeed with perfdata_service_raw. In the e=
xample I sent
> you, the metrics were 2 (CRITICAL) in perfdata_service_bin; OTOH they w=
ere 0 (NORMAL) in
> perfdata_service_raw. And the graphs continued not showing the guides f=
or
> warning/critical thresholds. At this point, I rolled back to release 0.=
100.7.

I have already noticed that with previous versions and I don't remember i=
f the reason
has been found yet.

> I've found performance problems also in 0.101.1, as I feel that it is m=
uch slower than
> 0.100.7 when reading the serviceperf.log file and putting it into the d=
atabase. In
> 0.100.7 I've got thousands of lines per second; in 0.101.1 this number =
never is greater
> than 70 lines/sec. And I'm running on a machine with 512 MB RAM, 2xInte=
l Xeon 3.06 GHz!
> I've tried to optimize MySQL settings to no avail, and this was other r=
eason that leaded
> me to roll back to 0.100.7.

Could you send us what this returns ?
perfparse-log2db <your options here> --show_config

I want to make sure that you don't enable something that will slow perfpa=
rse.

> Also, the documentation is a little confusing in this release. It took =
me some time
> until I understood that, with --default-perfdata I wouldn't have to use=
 crontab entries
> anymore to update the database. There's no mention of this in the docum=
entation, and if
> it sounds obvious for the developing team, it may be not so clear for t=
he users.

Yes, I'm not good at documentation, and Ben and Garry were too busy to he=
lp me. I should
have asked here on the mailing-list for some help :)

About crontab, perfparse-0.102 will include a daemon and provide more fea=
tures.
If somebody wants to help with beta-testing and documentation, please tel=
l us !

> Don't get me wrong: I find that perfparse is THE solution for gathering=
 performance data
> for Nagios. However, I feel that this wasn't the right time to release =
0.101.1 because
> it clearly lacks polishing and has rough edges on database architecture=
 and plugin
> parsing output.

0.101.1 was released after 23 devel releases and I needed feedback to kno=
w if I could
continue with my ideas or if I had to listen users.
When you develop on your own, sometimes, you make tools for you and they =
are too far
from users's needs. With 0.101.1, I wanted to be sure that it was OK, and=
 I considered
it as stable enough to make a public and official release.

> Why don't you add a compilation switch to disable these burning edge fe=
atures? It would
> make life easier to people that rely on perfparse for data gathering on=
 production
> systems.

What burning edge features ?
Except what I call storage modules (and only the mysql storage module is =
enabled in
perfparse-log2db), I don't understand what you are talking about that cou=
ld be disabled.

> []'s and keep the great work,

Thanks for the feedback. With 0.101.1, this is really necessary !

Yves
--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-users] 0.101.1 Statistics under Graph??

[Sand P. <Phi...@sy...>]

Hi,

I just draw a few graphs with the new Version and was pretty "shocked" th=
at the hole Statistics Part under the Graph are missing! Why did you remo=
ve that feature?
Would be great to have it back in 0.101.2 :-)

Regards,
Philipp



_____________________________

Philipp Sand
OC-CC-TEC-SYS

SYCOR GmbH
Heinrich-von-Stephan-Stra=DFe 1-5
D - 37073 G=F6ttingen

Telefon	+49 (0) 551 / 490 - 0
Telefax	+49 (0) 551 / 490 - 232468

phi...@sy...
www.sycor.de
------------------------------------------------



************************************************

sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie

www.sycor-plastics.de

************************************************




Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info=
rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge=
r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben=
achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4=
ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind=
liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht=
 ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu=
rde.

This e-mail is confidential and may contain personal and/or privileged in=
formation. If you are not the intended recipient please delete this e-mai=
l and all attachments immediately and inform us. The company sycor does n=
ot agree with contracts or contract obligations sent by e-mail, neither d=
o we transmit legally binding offers by e-mail, unless this is not expres=
sly agreed upon between the parties and documented in written form.

RES: RES: [Perfparse-users] Warning/critical values not going into the database... Again

[Paulo A. G. F. <pau...@pr...>]

Ben,

Please see my answers below.

Paulo Afonso Graner Fessel
Administrador de Ambiente e Sistemas UNIX
pau...@pr...
OWT
Fone: +55 (11) 3038-6554
Fax: +55 (11) 3038-6508
http://www.primesys.com.br

> The problem with the range.  Do you use a single value for=20
> the WARN and CRIT, or do you use the range format?  Can you=20
> please provide an example log line so that we can ensure=20
> there is no misunderstanding of the range and how it should=20
> be interpreted?

No, I use single values for WARN and CRIT:

1098196046      psdes01bill     /usr    DISK OK - free space: /usr 775 =
MB (31%):
        OK       /usr=3D775MB;2446;2471;0;2496

> However, this looks like a simple bug, thanks for finding this.
>=20
> The State calculation also looks like a simple bug although I=20
> have not yet looked at the code.  Again, if you can supply a=20
> line or two of raw log this would be extremely useful.

Unfortunately this is not possible at the moment, as I'm not running =
0.101.1 now. I will see if I can setup a test server to reproduce this =
here.

> Your problem is speed is surprising.  I test on a 800MHz=20
> low-memory Linux box, which ensures any speed problems slap=20
> me in the face fast.=20
> The difference between the old and new was about 10% during=20
> my testing.=20
>   Can you please give us more information about your setup. =20
> Is you MySQL local or on a remote server?

It's a local server.

> What method have you chosen to import the log information?

I've just told perfparse-log2db to read the service log, as I did other =
times with earlier versions of perfparse. It took more or less 4 hours =
to parse a 67 MB file.

> What commands do you run?

The equivalent of perfparse-log2db -r -s -l <pathtoservice.log>

> Lastly my apologies for the documentation.  This is beta=20
> code, deliberately not yet on version 1.0.  We obviously have=20
> some work to do here.

Ok. Stand by me for continuing support of PP.

[]'s
Paulo
=20
> Paulo Afonso Graner Fessel wrote:
>=20
> > Ben,
> >=20
> > I've found that perfparse has now the infrastructure to use=20
> ranges of warning/critical data, and the problem is that the=20
> database hasn't changed in order to use these values (as far=20
> as I can see, at least).
> >=20
> > Part of the problem is at save_bin_data at storage_mysql.c:
> >=20
> >         g_string_append_printf(s_SQL, ", %s",
> >                 getSafeD(perf->d[PERF_VALUE_WARN_START]));
> >         g_string_append_printf(s_SQL, ", %s",
> >                 getSafeD(perf->d[PERF_VALUE_CRIT_START]));
> >         g_string_append_printf(s_SQL, ", %s)",
> >                 getSafeD(perf->metric_state));
> >=20
> > I've changed it to
> >=20
> >         g_string_append_printf(s_SQL, ", %s",
> >                 getSafeD(perf->d[PERF_VALUE_WARN_END]));
> >         g_string_append_printf(s_SQL, ", %s",
> >                 getSafeD(perf->d[PERF_VALUE_CRIT_END]));
> >         g_string_append_printf(s_SQL, ", %s)",
> >                 getSafeD(perf->metric_state));
> >=20
> > and the data begun to show up in perfdata_service_bin.=20
> However, metric_state values were still wrong and=20
> inconsistent indeed with perfdata_service_raw. In the example=20
> I sent you, the metrics were 2 (CRITICAL) in=20
> perfdata_service_bin; OTOH they were 0 (NORMAL) in=20
> perfdata_service_raw. And the graphs continued not showing=20
> the guides for warning/critical thresholds. At this point, I=20
> rolled back to release 0.100.7.
> >=20
> > I've found performance problems also in 0.101.1, as I feel=20
> that it is=20
> > much slower than 0.100.7 when reading the
>=20
> serviceperf.log file and putting it into the database. In=20
> 0.100.7 I've got thousands of lines per second; in
>=20
> 0.101.1 this number never is greater than 70 lines/sec. And=20
> I'm running on a machine with 512 MB RAM, 2xIntel
>=20
> Xeon 3.06 GHz! I've tried to optimize MySQL settings to no=20
> avail, and this was other reason that leaded me to roll back=20
> to 0.100.7.
> >=20
> > Also, the documentation is a little confusing in this=20
> release. It took=20
> > me some time until I understood that, with
>=20
> --default-perfdata I wouldn't have to use crontab entries=20
> anymore to update the database. There's no mention
>=20
> of this in the documentation, and if it sounds obvious for=20
> the developing team, it may be not so clear for the users.
> >=20
> > Don't get me wrong: I find that perfparse is THE solution=20
> for gathering performance data for Nagios. However, I feel=20
> that this wasn't the right time to release 0.101.1 because it=20
> clearly lacks polishing and has rough edges on database=20
> architecture and plugin parsing output.
> >=20
> > Why don't you add a compilation switch to disable these=20
> burning edge features? It would make life easier to people=20
> that rely on perfparse for data gathering on production systems.
> >=20
> > []'s and keep the great work,
> >=20
> > Paulo Afonso Graner Fessel
> > Administrador de Ambiente e Sistemas UNIX=20
> pau...@pr...=20
> > OWT
> > Fone: +55 (11) 3038-6554
> > Fax: +55 (11) 3038-6508
> > http://www.primesys.com.br
> > =20
> > =20
> > =20
> > =20
> >=20
> >=20
> >>-----Mensagem original-----
> >>De: Ben Clewett [mailto:Be...@cl...] Enviada em:=20
> ter=E7a-feira,=20
> >>19 de outubro de 2004 04:25
> >>Para: Paulo Afonso Graner Fessel
> >>Cc: per...@li...
> >>Assunto: Re: [Perfparse-users] Warning/critical values not=20
> going into=20
> >>the database... Again
> >>
> >>Paulo,
> >>
> >>Can you please send me a sample of your data, I want to=20
> replicate and=20
> >>fix this problem.
> >>
> >>Regards,
> >>
> >>Ben Clewett.
> >>
> >>Paulo Afonso Graner Fessel wrote:
> >>
> >>
> >>>Hello, folks.
> >>>=20
> >>>I've just upgraded to 0.101.1 and I'm noticing that
> >>
> >>warning/critical
> >>
> >>>values from plugins are not getting into the database again. But=20
> >>>differently (and worst) than last time, seems that the
> >>
> >>state field of
> >>
> >>>perfdata_service_bin is also incorrect:
> >>>=20
> >>>
> >>
> >>+-------------+-----------------------------+-----------------
> >>------------+---------------------+----------+--------+-------
> >>---+--------+
> >>
> >>>| host_name   | service_description         |=20
> >>>metric                      | ctime               | value  =20
> >>
> >> | warn   |=20
> >>
> >>>critical | state  |
> >>>
> >>
> >>+-------------+-----------------------------+-----------------
> >>------------+---------------------+----------+--------+-------
> >>---+--------+
> >>
> >>>| D01         | Cache Hits                  |=20
> >>>lib                         | 2004-10-18 17:35:58 |   =20
> >>
> >>99.99 |      0=20
> >>
> >>>|        0 |      2 |
> >>>| D01         | Cache Hits                  |=20
> >>>buffer                      | 2004-10-18 17:35:58 |   =20
> >>
> >>99.95 |      0=20
> >>
> >>>|        0 |      2 |
> >>>
> >>
> >>+-------------+-----------------------------+-----------------
> >>------------+---------------------+----------+--------+-------
> >>---+--------+
> >>
> >>>In my definition of this particular service, I want these
> >>
> >>two metrics
> >>
> >>>to be as high as possible, with a maximum value of 100%.=20
> >>
> >>However, as
> >>
> >>>you can see, I don't have warning and critical values for
> >>
> >>this metric,
> >>
> >>>and also its state as determined by perfparse is 2 (CRITICAL); it=20
> >>>should be 0 actually (NORMAL).
> >>>=20
> >>>[]'s
> >>>=20
> >>>*Paulo Afonso Graner Fessel*
> >>>/Administrador de Ambiente e Sistemas UNIX/=20
> >>>pau...@pr... <mailto:pau...@pr...>
> >>>OWT
> >>>Fone: +55 (11) 3038-6554
> >>>Fax: +55 (11) 3038-6508
> >>>http://www.primesys.com.br <http://www.primesys.com.br/>
> >>>=20
> >>>=20
> >>>=20
> >>
> >>
> >=20
>=20
>=20

Re: RES: [Perfparse-users] Warning/critical values not going into the database... Again

[Ben C. <Be...@cl...>]

Paulo,

Thanks for the quality feedback on the new release.  I am sorry you have=20
experienced these problems and feel the need to retard back a version.=20
Hopefully we can ensure that future versions are back on track.

The problem with the range.  Do you use a single value for the WARN and=20
CRIT, or do you use the range format?  Can you please provide an example=20
log line so that we can ensure there is no misunderstanding of the range=20
and how it should be interpreted?

However, this looks like a simple bug, thanks for finding this.

The State calculation also looks like a simple bug although I have not=20
yet looked at the code.  Again, if you can supply a line or two of raw=20
log this would be extremely useful.

The storage of the range will require a big change to the database.  We=20
will be dropping the current binary storage table and replacing it with=20
two new tables.  One with just values.  One with peripheral information=20
like the Max/Min and Warn/Crit ranges.  This will give faster data=20
access and smaller table space.  Although at the penalty of a heavy=20
conversion process at that time.  In the mean while, I hope an=20
acceptable way can be found, as in the past, to use the available fields=20
to store the required data.

Your problem is speed is surprising.  I test on a 800MHz low-memory=20
Linux box, which ensures any speed problems slap me in the face fast.=20
The difference between the old and new was about 10% during my testing.=20
  Can you please give us more information about your setup.  Is you=20
MySQL local or on a remote server?  What method have you chosen to=20
import the log information?  What commands do you run?

Lastly my apologies for the documentation.  This is beta code,=20
deliberately not yet on version 1.0.  We obviously have some work to do=20
here.

Kind regards,

Ben Clewett.



Paulo Afonso Graner Fessel wrote:

> Ben,
>=20
> I've found that perfparse has now the infrastructure to use ranges of w=
arning/critical data, and the problem is that the database hasn't changed=
 in order to use these values (as far as I can see, at least).
>=20
> Part of the problem is at save_bin_data at storage_mysql.c:
>=20
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_WARN_START]));
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_CRIT_START]));
>         g_string_append_printf(s_SQL, ", %s)",
>                 getSafeD(perf->metric_state));
>=20
> I've changed it to
>=20
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_WARN_END]));
>         g_string_append_printf(s_SQL, ", %s",
>                 getSafeD(perf->d[PERF_VALUE_CRIT_END]));
>         g_string_append_printf(s_SQL, ", %s)",
>                 getSafeD(perf->metric_state));
>=20
> and the data begun to show up in perfdata_service_bin. However, metric_=
state values were still wrong and inconsistent indeed with perfdata_servi=
ce_raw. In the example I sent you, the metrics were 2 (CRITICAL) in perfd=
ata_service_bin; OTOH they were 0 (NORMAL) in perfdata_service_raw. And t=
he graphs continued not showing the guides for warning/critical threshold=
s. At this point, I rolled back to release 0.100.7.
>=20
> I've found performance problems also in 0.101.1, as I feel that it is m=
uch slower than 0.100.7 when reading the=20

serviceperf.log file and putting it into the database. In 0.100.7 I've=20
got thousands of lines per second; in

0.101.1 this number never is greater than 70 lines/sec. And I'm running=20
on a machine with 512 MB RAM, 2xIntel

Xeon 3.06 GHz! I've tried to optimize MySQL settings to no avail, and=20
this was other reason that leaded me to roll back to 0.100.7.
>=20
> Also, the documentation is a little confusing in this release. It took =
me some time until I understood that, with=20

--default-perfdata I wouldn't have to use crontab entries anymore to=20
update the database. There's no mention

of this in the documentation, and if it sounds obvious for the=20
developing team, it may be not so clear for the users.
>=20
> Don't get me wrong: I find that perfparse is THE solution for gathering=
 performance data for Nagios. However, I feel that this wasn't the right =
time to release 0.101.1 because it clearly lacks polishing and has rough =
edges on database architecture and plugin parsing output.
>=20
> Why don't you add a compilation switch to disable these burning edge fe=
atures? It would make life easier to people that rely on perfparse for da=
ta gathering on production systems.
>=20
> []'s and keep the great work,
>=20
> Paulo Afonso Graner Fessel
> Administrador de Ambiente e Sistemas UNIX
> pau...@pr...
> OWT
> Fone: +55 (11) 3038-6554
> Fax: +55 (11) 3038-6508
> http://www.primesys.com.br
> =20
> =20
> =20
> =20
>=20
>=20
>>-----Mensagem original-----
>>De: Ben Clewett [mailto:Be...@cl...]=20
>>Enviada em: ter=E7a-feira, 19 de outubro de 2004 04:25
>>Para: Paulo Afonso Graner Fessel
>>Cc: per...@li...
>>Assunto: Re: [Perfparse-users] Warning/critical values not=20
>>going into the database... Again
>>
>>Paulo,
>>
>>Can you please send me a sample of your data, I want to=20
>>replicate and fix this problem.
>>
>>Regards,
>>
>>Ben Clewett.
>>
>>Paulo Afonso Graner Fessel wrote:
>>
>>
>>>Hello, folks.
>>>=20
>>>I've just upgraded to 0.101.1 and I'm noticing that=20
>>
>>warning/critical=20
>>
>>>values from plugins are not getting into the database again. But=20
>>>differently (and worst) than last time, seems that the=20
>>
>>state field of=20
>>
>>>perfdata_service_bin is also incorrect:
>>>=20
>>>
>>
>>+-------------+-----------------------------+-----------------
>>------------+---------------------+----------+--------+-------
>>---+--------+
>>
>>>| host_name   | service_description         |=20
>>>metric                      | ctime               | value  =20
>>
>> | warn   |=20
>>
>>>critical | state  |
>>>
>>
>>+-------------+-----------------------------+-----------------
>>------------+---------------------+----------+--------+-------
>>---+--------+
>>
>>>| D01         | Cache Hits                  |=20
>>>lib                         | 2004-10-18 17:35:58 |   =20
>>
>>99.99 |      0=20
>>
>>>|        0 |      2 |
>>>| D01         | Cache Hits                  |=20
>>>buffer                      | 2004-10-18 17:35:58 |   =20
>>
>>99.95 |      0=20
>>
>>>|        0 |      2 |
>>>
>>
>>+-------------+-----------------------------+-----------------
>>------------+---------------------+----------+--------+-------
>>---+--------+
>>
>>>In my definition of this particular service, I want these=20
>>
>>two metrics=20
>>
>>>to be as high as possible, with a maximum value of 100%.=20
>>
>>However, as=20
>>
>>>you can see, I don't have warning and critical values for=20
>>
>>this metric,=20
>>
>>>and also its state as determined by perfparse is 2 (CRITICAL); it=20
>>>should be 0 actually (NORMAL).
>>>=20
>>>[]'s
>>>=20
>>>*Paulo Afonso Graner Fessel*
>>>/Administrador de Ambiente e Sistemas UNIX/=20
>>>pau...@pr... <mailto:pau...@pr...>
>>>OWT
>>>Fone: +55 (11) 3038-6554
>>>Fax: +55 (11) 3038-6508
>>>http://www.primesys.com.br <http://www.primesys.com.br/>
>>>=20
>>>=20
>>>=20
>>
>>
>=20

RES: [Perfparse-users] Warning/critical values not going into the database... Again

[Paulo A. G. F. <pau...@pr...>]

Ben,

I've found that perfparse has now the infrastructure to use ranges of =
warning/critical data, and the problem is that the database hasn't =
changed in order to use these values (as far as I can see, at least).

Part of the problem is at save_bin_data at storage_mysql.c:

        g_string_append_printf(s_SQL, ", %s",
                getSafeD(perf->d[PERF_VALUE_WARN_START]));
        g_string_append_printf(s_SQL, ", %s",
                getSafeD(perf->d[PERF_VALUE_CRIT_START]));
        g_string_append_printf(s_SQL, ", %s)",
                getSafeD(perf->metric_state));

I've changed it to

        g_string_append_printf(s_SQL, ", %s",
                getSafeD(perf->d[PERF_VALUE_WARN_END]));
        g_string_append_printf(s_SQL, ", %s",
                getSafeD(perf->d[PERF_VALUE_CRIT_END]));
        g_string_append_printf(s_SQL, ", %s)",
                getSafeD(perf->metric_state));

and the data begun to show up in perfdata_service_bin. However, =
metric_state values were still wrong and inconsistent indeed with =
perfdata_service_raw. In the example I sent you, the metrics were 2 =
(CRITICAL) in perfdata_service_bin; OTOH they were 0 (NORMAL) in =
perfdata_service_raw. And the graphs continued not showing the guides =
for warning/critical thresholds. At this point, I rolled back to release =
0.100.7.

I've found performance problems also in 0.101.1, as I feel that it is =
much slower than 0.100.7 when reading the serviceperf.log file and =
putting it into the database. In 0.100.7 I've got thousands of lines per =
second; in 0.101.1 this number never is greater than 70 lines/sec. And =
I'm running on a machine with 512 MB RAM, 2xIntel Xeon 3.06 GHz! I've =
tried to optimize MySQL settings to no avail, and this was other reason =
that leaded me to roll back to 0.100.7.

Also, the documentation is a little confusing in this release. It took =
me some time until I understood that, with --default-perfdata I wouldn't =
have to use crontab entries anymore to update the database. There's no =
mention of this in the documentation, and if it sounds obvious for the =
developing team, it may be not so clear for the users.

Don't get me wrong: I find that perfparse is THE solution for gathering =
performance data for Nagios. However, I feel that this wasn't the right =
time to release 0.101.1 because it clearly lacks polishing and has rough =
edges on database architecture and plugin parsing output.

Why don't you add a compilation switch to disable these burning edge =
features? It would make life easier to people that rely on perfparse for =
data gathering on production systems.

[]'s and keep the great work,

Paulo Afonso Graner Fessel
Administrador de Ambiente e Sistemas UNIX
pau...@pr...
OWT
Fone: +55 (11) 3038-6554
Fax: +55 (11) 3038-6508
http://www.primesys.com.br
=20
=20
=20
=20

> -----Mensagem original-----
> De: Ben Clewett [mailto:Be...@cl...]=20
> Enviada em: ter=E7a-feira, 19 de outubro de 2004 04:25
> Para: Paulo Afonso Graner Fessel
> Cc: per...@li...
> Assunto: Re: [Perfparse-users] Warning/critical values not=20
> going into the database... Again
>=20
> Paulo,
>=20
> Can you please send me a sample of your data, I want to=20
> replicate and fix this problem.
>=20
> Regards,
>=20
> Ben Clewett.
>=20
> Paulo Afonso Graner Fessel wrote:
>=20
> > Hello, folks.
> > =20
> > I've just upgraded to 0.101.1 and I'm noticing that=20
> warning/critical=20
> > values from plugins are not getting into the database again. But=20
> > differently (and worst) than last time, seems that the=20
> state field of=20
> > perfdata_service_bin is also incorrect:
> > =20
> >=20
> +-------------+-----------------------------+-----------------
> ------------+---------------------+----------+--------+-------
> ---+--------+
> > | host_name   | service_description         |=20
> > metric                      | ctime               | value  =20
>  | warn   |=20
> > critical | state  |
> >=20
> +-------------+-----------------------------+-----------------
> ------------+---------------------+----------+--------+-------
> ---+--------+
> > | D01         | Cache Hits                  |=20
> > lib                         | 2004-10-18 17:35:58 |   =20
> 99.99 |      0=20
> > |        0 |      2 |
> > | D01         | Cache Hits                  |=20
> > buffer                      | 2004-10-18 17:35:58 |   =20
> 99.95 |      0=20
> > |        0 |      2 |
> >=20
> +-------------+-----------------------------+-----------------
> ------------+---------------------+----------+--------+-------
> ---+--------+
> > In my definition of this particular service, I want these=20
> two metrics=20
> > to be as high as possible, with a maximum value of 100%.=20
> However, as=20
> > you can see, I don't have warning and critical values for=20
> this metric,=20
> > and also its state as determined by perfparse is 2 (CRITICAL); it=20
> > should be 0 actually (NORMAL).
> > =20
> > []'s
> > =20
> > *Paulo Afonso Graner Fessel*
> > /Administrador de Ambiente e Sistemas UNIX/=20
> > pau...@pr... <mailto:pau...@pr...>
> > OWT
> > Fone: +55 (11) 3038-6554
> > Fax: +55 (11) 3038-6508
> > http://www.primesys.com.br <http://www.primesys.com.br/>
> > =20
> > =20
> > =20
>=20
>=20

Re: [Perfparse-users] Warning/critical values not going into the database... Again

[Ben C. <Be...@cl...>]

Paulo,

Can you please send me a sample of your data, I want to replicate and 
fix this problem.

Regards,

Ben Clewett.

Paulo Afonso Graner Fessel wrote:

> Hello, folks.
>  
> I've just upgraded to 0.101.1 and I'm noticing that warning/critical 
> values from plugins are not getting into the database again. But 
> differently (and worst) than last time, seems that the state field of 
> perfdata_service_bin is also incorrect:
>  
> +-------------+-----------------------------+-----------------------------+---------------------+----------+--------+----------+--------+
> | host_name   | service_description         | 
> metric                      | ctime               | value    | warn   | 
> critical | state  |
> +-------------+-----------------------------+-----------------------------+---------------------+----------+--------+----------+--------+
> | D01         | Cache Hits                  | 
> lib                         | 2004-10-18 17:35:58 |    99.99 |      0 
> |        0 |      2 |
> | D01         | Cache Hits                  | 
> buffer                      | 2004-10-18 17:35:58 |    99.95 |      0 
> |        0 |      2 |
> +-------------+-----------------------------+-----------------------------+---------------------+----------+--------+----------+--------+
> In my definition of this particular service, I want these two metrics to 
> be as high as possible, with a maximum value of 100%. However, as you 
> can see, I don't have warning and critical values for this metric, and 
> also its state as determined by perfparse is 2 (CRITICAL); it should be 
> 0 actually (NORMAL).
>  
> []'s
>  
> *Paulo Afonso Graner Fessel*
> /Administrador de Ambiente e Sistemas UNIX/
> pau...@pr... <mailto:pau...@pr...>
> OWT
> Fone: +55 (11) 3038-6554
> Fax: +55 (11) 3038-6508
> http://www.primesys.com.br <http://www.primesys.com.br/>
>  
>  
>