RE: [Perfparse-users] No data in serviceperf.log file.

[Cook, G. <GW...@ma...>]

Yes. I have not spent much time yet actually installing perfparse. I
took a quick look at it last Thursday before taking a little vacation. I
hope to download the new version and continue working with it this week,
as well as continue work on the HOW-TO. At this point, the HOW-TO is
current up to the point where I needed to turn on Performance Data
processing via the Nagios web page. So, it's really more of a 'Nagios
Performance Data HOW-TO'. So, I'll see if I can clean this up a bit and
send it over to you later today.

Garry W. Cook, CCNA
Network Infrastructure Manager
MACTEC, Inc. - http://www.mactec.com/
303.308.6228 (Office) - 720.220.1862 (Mobile)

Ben Clewett wrote:
> Garry, I am very glad to hear that it works for you.  It does sound a
> bit odd.  I never had to turn it on here.  Can you remember
> ever turning
> it off?
>=20
> You you be able to put together a check-list of all the
> things which you
> had to do to get the data.  Which we can put live on the site
> and link
> from the web page?  I dread to think from the 130+ people who have
> downloaded perfparse, how many have also given up because of
> this problem.
>=20
> Well, enjoy using the product,
>=20
> Ben
>=20
> Cook, Garry wrote:
>=20
>> No, that wasn't the issue. However, I did finally find the solution!
>> I opened my Nagios web page, and went to the 'Process Info' page. At
>> the bottom of the Process Information box I saw:
>>=20
>> "Performance Data Being Processed?     No"
>>=20
>> So, in the 'Process Commands' box I clicked on "Enable performance
>> data". This solved the problem.
>>=20
>> Did I miss something somewhere? Shouldn't the changes to the config
>> files make performance data active? In other words, is this a bug
>> that I've found or do you think it was Ethan's intention to have us
>> enable it in the configs and then have to manually turn it on via
>> the web page? If it was intentional, then the docs should be updated.
>>=20
>> I've copied Ethan directly on this message, rather than clutter up
>> the Nagios list any further.=20
>>=20
>> -g