pcp
[Top] [All Lists]

Re: PCP deployment with some monitored servers behind a firewall

To: Tadej JaneÅ <tadej.j@xxxxxx>
Subject: Re: PCP deployment with some monitored servers behind a firewall
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Wed, 2 Sep 2015 08:59:08 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1441198340.16058.21.camel@tlinux64>
References: <1440753655.4840.44.camel@tlinux64> <y0m1tenlc5e.fsf@xxxxxxxx> <1441198340.16058.21.camel@tlinux64>
User-agent: Mutt/1.4.2.2i
Hi -

On Wed, Sep 02, 2015 at 02:52:20PM +0200, Tadej JaneÅ wrote:
> [...]
> In order to reliably keep this reverse SSH tunnel open, I'm using
> autossh [1]:
> autossh -M 20000 -N -R 6543:localhost:44321 monitoring_server

Tood tips, thanks.


> > That's it.  pmie won't work across that tunnel, due to bugs just
> > recently fixed (somewhere in the merge queue), but pmlogger will be
> > fine.
> 
> Can you give me a link/pointer to the fix(es)?

Certainly:
http://oss.sgi.com/pipermail/pcp/2015-August/008119.html


> I have another question regarding this setup.
> Is it possible to give the machines which pmmgr will be referring to as
> 'localhost:6543', 'localhost:6544', ... a nicer name/alias which can be
> used by pmlogger and web UI tools like Vector and Grafana?

Certainly.  pmmgr can use the remote pmcd-supplied host names for
building directory names, not the ip:port hostspec strings, so this
should just work for you already.  (See the "hostid-metrics" part in
[man pmmgr] for more.)

Vector doesn't operate via pmmgr / log files, so to make it talk
across a tunnel, use the "2. central pmwebd ..." vector deployment
model, and "localhost:6544" etc. as the vector Hostspec.

- FChE

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