On Wed, 2015-09-02 at 08:59 -0400, Frank Ch. Eigler wrote:
> On Wed, Sep 02, 2015 at 02:52:20PM +0200, Tadej JaneÅ wrote:
>
> > > 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
Thanks! I hope it gets reviewed soon.
> > 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.)
Nice. I just tested it and pmmgr indeed refers to a machine via its host
name.
> 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.
Ok, understood. I tried it and it works. Having to specify:
"hostname=localhost:44323" and "hostspec=localhost:6544" feels a little
clumsy, though.
Another thing, what is the preferred way to report bugs?
I want to report a problem with tool tips on flot.js graphs in Grafana.
Regards,
Tadej
|