pcp
[Top] [All Lists]

Re: [pcp] elasticsearch PMDA question

To: Alec Ten Harmsel <alec@xxxxxxxxxxxxxxxxxx>
Subject: Re: [pcp] elasticsearch PMDA question
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 15 Mar 2016 17:31:05 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20160315164834.GA4224@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <20160314141105.GA1513@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <941490186.30277739.1457987906285.JavaMail.zimbra@xxxxxxxxxx> <20160314212939.GA4200@greenbeast> <659848817.30294126.1457992411353.JavaMail.zimbra@xxxxxxxxxx> <20160315164834.GA4224@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: bh0rpLFCjps+YQf2OAFGDbxnBiWbxw==
Thread-topic: elasticsearch PMDA question

----- Original Message -----
> On Mon, Mar 14, 2016 at 05:53:31PM -0400, Nathan Scott wrote:
> > ----- Original Message -----
> > > [...]
> > > I see that a configuration file PCP_PMDAS_DIR/elasticsearch/es.conf is
> > > parsed by the PMDA. I was thinking that it would be possible to add a
> > > new variable, something like $all_node_stats. It would default to false,
> > > so only metrics from localhost would be fetched. It could be set true by
> > > that configuration file.
> > 
> > Good solution, that'd work well.
> 
> I am planning on doing this unless you say otherwise. I like the
> approach you're suggesting, but I don't want to break
> backwards-compatibility unless I'm explicitly told that it's OK.

Yep, good call - go for it.  Thanks Alec.

cheers.

--
Nathan

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