[gpfsug-discuss] problems with collector 5 and grafana bridge 3

Grunenberg, Renar Renar.Grunenberg at huk-coburg.de
Wed Apr 25 13:11:53 BST 2018


Hallo Ivano
We use filter only. For cpu_user ->node = pm_filter($byNode)

Regards Renar



Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:  09561 96-44110
Telefax:  09561 96-44104
E-Mail:   Renar.Grunenberg at huk-coburg.de
Internet: www.huk.de
=======================================================================
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
=======================================================================
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
=======================================================================

-----Ursprüngliche Nachricht-----
Von: Ivano Talamo [mailto:Ivano.Talamo at psi.ch]
Gesendet: Mittwoch, 25. April 2018 13:37
An: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>; Grunenberg, Renar <Renar.Grunenberg at huk-coburg.de>
Betreff: Re: [gpfsug-discuss] problems with collector 5 and grafana bridge 3

Hello Renar,

I also changed the bridge to openTSDB 2.3 and set it use query2port. I
was only not sure that this was the multi-threaded one.

But are you using the pipe-based metrics (like "hostname|CPU|cpu_user")
or you use filters?

Thanks,
Ivano

Il 25/04/18 12:44, Grunenberg, Renar ha scritto:
> Hallo Ivano,
>
> we change the bridge port to query2port this is the multithreaded Query port. The Bridge in Version3 select these port automatically if the pmcollector config is updated(/opt/IBM/zimon/ZIMonCollector.cfg).
> # The query port number defaults to 9084.
> queryport = "9084"
> query2port = "9094"
> We use 5.0.0.2 here. What we also change was in the Datasource Panel for the bridge in Grafana the openTSDB to ==2.3. Hope this help.
>
> Regards Renar
>
>
>
> Renar Grunenberg
> Abteilung Informatik – Betrieb
>
> HUK-COBURG
> Bahnhofsplatz
> 96444 Coburg
> Telefon:  09561 96-44110
> Telefax:  09561 96-44104
> E-Mail:   Renar.Grunenberg at huk-coburg.de
> Internet: www.huk.de
> =======================================================================
> HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
> Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
> Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
> Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
> Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
> =======================================================================
> Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.
>
> This information may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this information in error) please notify the
> sender immediately and destroy this information.
> Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
> =======================================================================
>
> -----Ursprüngliche Nachricht-----
> Von: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] Im Auftrag von Ivano Talamo
> Gesendet: Mittwoch, 25. April 2018 10:47
> An: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
> Betreff: [gpfsug-discuss] problems with collector 5 and grafana bridge 3
>
> Hi all,
>
> I am actually testing the collector shipped with Spectrum Scale 5.0.0-1
> together with the latest grafana bridge (version 3). At the UK UG
> meeting I learned that this is the multi-threaded setup, so hopefully we
> can get better performances.
>
> But we are having a problem. Our existing grafana dashboard have metrics
> like eg. "hostname|CPU|cpu_user". It was working and it also had a very
> helpful completion when creating new graphs.
> After the upgrade these metrics are not recognized anymore, and we are
> getting the following errors in the grafana bridge log file:
>
> 2018-04-25 09:35:24,999 - zimonGrafanaIntf - ERROR - Metric
> hostnameNetwork|team0|netdev_drops_s cannot be found. Please check if
> the corresponding sensor is configured
>
> The only way I found to make them work is using only the real metric
> name, eg "cpu_user" and then use filter to restrict to a host
> ('node'='hostname'). The problem is that in many cases the metric is
> complex, eg. you want to restrict to a filesystem, to a fileset, to a
> network interface. And is not easy to get the field names to be used in
> the filters.
>
> So my questions are:
> - is this supposed to be like that or the old metrics name can be
> enabled somehow?
> - if it has to be like that, how can I get the available field names to
> use in the filters?
>
>
> And then I saw in the new collector config file this:
>
> queryport = "9084"
> query2port = "9094"
>
> Which one should be used by the bridge?
>
> Thank you,
> Ivano
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>


More information about the gpfsug-discuss mailing list