Ad Widget

Collapse

Hosted added by discovery FQDN

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rblumenthal
    Junior Member
    • May 2017
    • 11

    #1

    Hosted added by discovery FQDN

    Hey folks,

    I have a discovery rule set up and it is working exactly as it should, it adds the hosts and does a few other things that I would like. When it adds the host it adds the full FQDN. On the client itself (Windows), the agent log shows the host not found message and lists the hostname without the FQDN. Once I remove the FQDN from the web, the message no longer appears in the log. My question, how can I have the FQDN not added when a new host is discovered so I do not need to modify in the web?

    Thanks

    PS: My agent config has this for the hostname if it helps: HostnameItem=system.hostname

    I use the same config for every host so I do not need to manually touch each client.
  • rblumenthal
    Junior Member
    • May 2017
    • 11

    #2
    Anyone? I'd rather not have to go in after the fact and remove the FQDN but if I need to I will, just odd why this happens. Perhaps DNS related? We use an appliance that hosts our AD domain (as well as many other domains)

    Comment

    • ovas
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Apr 2017
      • 138

      #3
      Hello rblumenthal!

      What if you set the host uniqueness criteria to system.hostname like this in discovery rule http://prntscr.com/f99cne?

      Comment

      Working...