pcp
[Top] [All Lists]

Re: [pcp] nginx PMDA error

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: [pcp] nginx PMDA error
From: Tadej JaneÅ <tadej.j@xxxxxx>
Date: Thu, 10 Sep 2015 15:02:41 +0200
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20150909153547.GB1788@xxxxxxxxxx>
References: <1441613884.8358.33.camel@tlinux64> <y0m37yqkqph.fsf@xxxxxxxx> <1441790097.27574.20.camel@tlinux64> <20150909125102.GD16438@xxxxxxxxxx> <1441811714.27574.80.camel@tlinux64> <20150909153547.GB1788@xxxxxxxxxx>
Hi Frank,

On Wed, 2015-09-09 at 11:35 -0400, Frank Ch. Eigler wrote:
> 
> I'm really not familiar with the insides of that pmda, but there
> is not that much going on.  Check it out - it's just a short perl
> script.  It does a http fetch on "http://localhost/nginx_status";
> (or some other location overridden in eval'd nginx.conf).  The
> resulting data is parsed with a blunt
> 
>      @nginx_status = ($response->decoded_content =~ m/(\d+)/gm);
> 
> and then metrics are fetched from that array, indexed by
> the item number (e.g. 6).  
> 
> So if I had to diagnose this bad boy, I'd start with a hand-fetched
> nginx_status result file, and insert some tracing to dump
> @nginx_status after the parse process.

Thanks for these debugging tips!

As I wrote in another post, I missed the part that I should configure
nginx to export the stats. Apart from the issues with SELinux denials, I
was able to make it work.

Thanks and best regards,
Tadej

<Prev in Thread] Current Thread [Next in Thread>