Open an issue please.
Michael
Am Samstag, 10. Januar 2015 schrieb Yannick Charton :
> Hi Michael,
>
> Updated my test server from 2.2.2-1 to last stable release 2.2.3-1
> ============================================================
> Package Arch Version
> ============================================================
> icinga2 x86_64 2.2.3-1.el7.centos
> icinga2-bin x86_64 2.2.3-1.el7.centos
> icinga2-classicui-config x86_64 2.2.3-1.el7.centos
> icinga2-common x86_64 2.2.3-1.el7.centos
> icinga2-debuginfo x86_64 2.2.3-1.el7.centos
> icinga2-doc x86_64 2.2.3-1.el7.centos
> icinga2-ido-mysql x86_64 2.2.3-1.el7.centos
> icinga2-ido-pgsql x86_64 2.2.3-1.el7.centos
>
> Same "bad" performance data format.
>
> Icinga 2 enabled feature list:
> [root@HP ~]# icinga2 feature list
> Disabled features: api gelf graphite ido-pgsql
> Enabled features: checker command compatlog debuglog icingastatus
> ido-mysql livestatus mainlog notification perfdata statusdata syslog
> [root@HP ~]#
>
>
> Small configuration exemple:
>
> - CheckCommand configured in commands.conf:
>
> /* CheckCommand objects */
>
> object CheckCommand "Linux_interfacetable_v3t" {
> import "plugin-check-command"
> command = [ CustomPluginDir + "/check_interface_table_v3t.pl" ]
> arguments = {
> "-H" = "$host_query$"
> "-h" = "$host_display$"
> "-C" = "$snmp_community$"
> "-P" = "$snmp_port$"
> "-2" = {
> set_if = "$snmp_v2$"
> }
> "-f" = {
> set_if = "$snmp_perf$"
> }
> }
>
> vars.host_query = "$address$"
> vars.host_display = "$host.display_name$"
> vars.snmp_community = "public"
> vars.snmp_port = 161
> vars.snmp_v2 = true
> vars.snmp_perf = true
> }
>
>
> - Service configured for all linux servers in services.conf:
>
> apply Service "network interfaces" {
> import "generic-service"
> check_command = "Linux_interfacetable_v3t"
> assign where host.address && host.vars.os == "Linux"
> }
>
>
>
> > Can you verify that the CheckCommand defined in Icinga 2 configuration
> > (post it here) matches the manually executed plugin output?
> >
> > I suspect that there's a difference in labelling the perfdata output
> > somewhere.
>
> I don't understand exactly what you're looking for. The performance data
> output returned by icinga2 and viewed in service details in the classicui
> cannot be generated by the plugin. So I guess it has been modified by the
> PerfdataWriter feature.
>
> Best regards,
> Yannick
>
>
> *Objet :* Re: [icinga-users] check_multi plugin output format not
> supported in icinga2?
>
> I will see that this evening: confirm the version of all icinga2 elements,
> list all the enabled features, and post the configuration (CheckCommand,
> service definition,...).
> Best regards,
> Yannick
>
>
> ------------------------------
> *De :* Michael Friedrich <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
> *À :* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> *Envoyé le :* Vendredi 9 janvier 2015 10h03
> *Objet :* Re: [icinga-users] check_multi plugin output format not
> supported in icinga2?
>
>
>
> Am 09.01.2015 um 09:57 schrieb Yannick Charton:
> > Hi Michael,
> >
> > No access to my server right now, but it should be as following. Very
> > fresh and very simple install, done especially for this issue.
> >
> >> - installation method (packages, distribution)
> > os: centos 7
> > icinga2 + classicui: last release via rpm (2.2.2-1)
> >
> >> - addons/features involved and their version
> > pnp4nagios: last release 0.6.25 installed via sources
> > interfacetable_v3t plugin, last git snapshot (0.05-2a).
>
> Hm. The reason I was asking is a change involved with PerfdataWriter and
> perfdata handling in 2.2.x. Older versions had this issue of parsing the
> performance in all situations, not only for Graphite and changing the
> order somewhat.
>
> That has been fixed and the performance data string is not touched but
> directly passed from icinga2 as caller to the PerfdataWriter feature.
>
> Can you verify that the CheckCommand defined in Icinga 2 configuration
> (post it here) matches the manually executed plugin output?
>
> I suspect that there's a difference in labelling the perfdata output
> somewhere.
>
> Kind regards,
> Michael
>
> >
> > Best regards,
> > Yannick
> >
> > ------------------------------------------------------------------------
> > *De :* Michael Friedrich <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
> > *À :* [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> > *Envoyé le :* Vendredi 9 janvier 2015 9h39
> > *Objet :* Re: [icinga-users] check_multi plugin output format not
> > supported in icinga2?
> >
> > Am 09.01.2015 um 08:56 schrieb Yannick Charton:
> > > Hi all,
> > >
> > > Recently, one user of my plugin Interfacetable_v3t plugin reported a
> > > problem when using it with icinga2 + pnp4nagios.
> >
> > Always provide the initial information required, such as
> >
> > - installation method (packages, distribution)
> > - icinga2 --version
> > - addons/features involved and their version
> >
> > kind regards,
> > Michael
> >
> >
> >
> >
> >
> > >
> > > I successfully reproduced the situation on a fresh icinga2 install,
> and
> > > found that the format of the performance data returned by the plugin
> is
> > > not in the expected one. Indeed, my plugin returns the performance
> data
> > > in a check_multi format.
> > >
> > > In command line, the performance data are:
> > > Interface_global::check_interface_table_global::time=0.07s;;;;
> > > uptime=451135s;;;; watched=3;;;; useddelta=3s;;;; ports=2;;;;
> > > freeports=2;;;; adminupfree=2;;;;
> > > If_lo::check_interface_table_port::OperStatus=1;;;0;
> > > BpsIn=0;10100000;10100000;0;10000000
> > > BpsOut=0;10100000;10100000;0;10000000 PpsInErr=0;1000;5000;0;
> > > PpsOutErr=0;1000;5000;0; PpsInDiscard=0;1000;5000;0;
> > > PpsOutDiscard=0;1000;5000;0;
> > > If_eno1::check_interface_table_port::OperStatus=1;;;0;
> > > BpsIn=0;1010000000;1010000000;0;1000000000
> > > BpsOut=0;1010000000;1010000000;0;1000000000 PpsInErr=0;1000;5000;0;
> > > PpsOutErr=0;1000;5000;0; PpsInDiscard=0;1000;5000;0;
> > > PpsOutDiscard=0;1000;5000;0;
> > > If_eno2::check_interface_table_port::OperStatus=2;;;0; BpsIn=0;;;0;
> > > BpsOut=0;;;0; PpsInErr=0;1000;5000;0; PpsOutErr=0;1000;5000;0;
> > > PpsInDiscard=0;1000;5000;0; PpsOutDiscard=0;1000;5000;0;
> > >
> > > The performance data returned by Icinga2 are:
> > > Interface_global::check_interface_table_global::time=0.09s;;;;
> > > Interface_global::check_interface_table_global::uptime=453660s;;;;
> > > Interface_global::check_interface_table_global::watched=3;;;;
> > > Interface_global::check_interface_table_global::useddelta=780s;;;;
> > > Interface_global::check_interface_table_global::ports=2;;;;
> > > Interface_global::check_interface_table_global::freeports=1;;;;
> > > Interface_global::check_interface_table_global::adminupfree=1;;;;
> > > If_lo::check_interface_table_port::OperStatus=1;;;0;
> > >
> >
> If_lo::check_interface_table_port::BpsIn=2659.52;10100000;10100000;0;10000000
> > >
> >
> If_lo::check_interface_table_port::BpsOut=2659.52;10100000;10100000;0;10000000
> > > If_lo::check_interface_table_port::PpsInErr=0;1000;5000;0;
> > > If_lo::check_interface_table_port::PpsOutErr=0;1000;5000;0;
> > > If_lo::check_interface_table_port::PpsInDiscard=0;1000;5000;0;
> > > If_lo::check_interface_table_port::PpsOutDiscard=0;1000;5000;0;
> > > If_eno1::check_interface_table_port::OperStatus=1;;;0;
> > >
> >
> If_eno1::check_interface_table_port::BpsIn=6182.48;1010000000;1010000000;0;1000000000
> > >
> >
> If_eno1::check_interface_table_port::BpsOut=45638.64;1010000000;1010000000;0;1000000000
> > > If_eno1::check_interface_table_port::PpsInErr=0;1000;5000;0;
> > > If_eno1::check_interface_table_port::PpsOutErr=0;1000;5000;0;
> > > If_eno1::check_interface_table_port::PpsInDiscard=0;1000;5000;0;
> > > If_eno1::check_interface_table_port::PpsOutDiscard=0;1000;5000;0;
> > > If_eno2::check_interface_table_port::OperStatus=2;;;0;
> > > If_eno2::check_interface_table_port::BpsIn=0;;;0;
> > > If_eno2::check_interface_table_port::BpsOut=0;;;0;
> > > If_eno2::check_interface_table_port::PpsInErr=0;1000;5000;0;
> > > If_eno2::check_interface_table_port::PpsOutErr=0;1000;5000;0;
> > > If_eno2::check_interface_table_port::PpsInDiscard=0;1000;5000;0;
> > > If_eno2::check_interface_table_port::PpsOutDiscard=0;1000;5000;0;
> > >
> > > I didn't find any info about the combinaison icinga2 + check_multi. Is
> > > there a special configuration option to use in the CheckCommand
> > > definition, to be able to return the performance data in a check_multi
> > > format? Or is it a bug? As I didn't have time to play with Icinga2
> yet,
> > > I don't know the subtlety of the service/checkcommand configurations
> in
> > > this new release, so I prefer to ask before opening a new issue.
> > >
> > > Another solution would be to work on the pnp4nagios xml file
> generation,
> > > where most of the ds are missing. For exemple, for Interface_global in
> > > this exemple, the xml file only contains the last ds which is
> > adminupfree.
> > >
> > > Best regards, and happy new year!
> > > Yannick (aka Tontonitch)
> >
> > >
> > >
> > > _______________________________________________
> > > icinga-users mailing list
> > > [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> <mailto:
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
> > > https://lists.icinga.org/mailman/listinfo/icinga-users
> > >
> >
> >
> > --
> > DI (FH) Michael Friedrich
> >
> > [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> <mailto:
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> ||
> > icinga open source monitoring
> > https://twitter.com/dnsmichi <https://twitter.com/dnsmichi>|| lead core
> > developer
> > [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> <mailto:
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> ||
> > https://www.icinga.org/team
> > irc.freenode.net/icinga || dnsmichi
> > _______________________________________________
> > icinga-users mailing list
> > [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');> <mailto:
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>>
> > https://lists.icinga.org/mailman/listinfo/icinga-users
> >
> >
> >
> >
> >
> > _______________________________________________
> > icinga-users mailing list
> > [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> > https://lists.icinga.org/mailman/listinfo/icinga-users
> >
>
>
> --
> Michael Friedrich, DI (FH)
> Application Developer
>
> NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg
> Tel: +49 911 92885-0 | Fax: +49 911 92885-77
> GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461
> http://www.netways.de | [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
>
> ** OSDC 2015 - April - osdc.de **
> ** Puppet Camp Berlin 2015 - April - netways.de/puppetcamp **
> ** OSBConf 2015 - September – osbconf.org **
>
>
>
> _______________________________________________
> icinga-users mailing list
> [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>
> https://lists.icinga.org/mailman/listinfo/icinga-users
>
>
>
>
>
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
