#22 exporter exports blank values for display_name

closed
nobody
None
1
2014-10-19
2013-06-12
Dale Blount
No

Hello.

The nagios exporter appears to export the value for display_name, even if it's blank.

Since this parameter is optional to nagios, it hasn't been filled out for most hosts on my install.

When I exported this to nagios, hosts.cfg is full of lines looking like this:

display_name

which in-turn causes blank display names in the Icinga Web-UI.

Now of course the simple fix is to fill this out, but it would be cleaner if the exporter handled this better.

A simple workaround for now is:

grep -v display_name hosts.cfg > hosts.tmp
mv hosts.tmp hosts.cfg

Thanks,

Dale

Discussion

  • The_Invisible

    The_Invisible - 2013-06-18

    Hi Dale,

    thanks for your request. This should not be a big issue and will be included in the next release. Stay tuned for the next few git commits.

    Regards
    Rene

     
  • The_Invisible

    The_Invisible - 2013-06-24
    • status: open --> accepted
     
  • Dale Blount

    Dale Blount - 2013-07-22

    I've had another problem possibly related to this. Importing services from fruity left display_name = NULL. Adding a new host and leaving the (optional) display_name empty, sets the display_name field for that service to "" in the DB, not NULL so it exports as blank instead.

     
  • The_Invisible

    The_Invisible - 2013-11-15

    Hello,

    this is fixed now in current git dev branch and will be included in next release. Please give it a try and give feedback.

    Regards
    Rene

     
  • The_Invisible

    The_Invisible - 2013-11-15
    • status: accepted --> pending
     
  • The_Invisible

    The_Invisible - 2013-12-06
    • status: pending --> closed
     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks