[ZBXNEXT-3085] Discovery Action -> Host add with none DNS value Created: 2016 Jan 06  Updated: 2017 Nov 09

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.4.6
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Colum Flannigan Assignee: Unassigned
Resolution: Unresolved Votes: 4
Labels: dns, networkdiscovery
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL 6, VMWare Guest



 Description   

Is it possible that during the action "Discovery -> Operation -> Add Host" that you can specify a none DNS value??

Perhaps being able to specify a zabbix agent key value like agent.hostname will work. We currently do not add our domain name "example.com" to our zabbix host entries and during the Discovery process it creates the entry with the full FQDN "server1.example.com".

With this we have to manually go into Zabbix and change this value as polling does not occur as we have the "Hostname" value in the agent configuration populated with just the hostname and not the FQDN name.

Agent Config Example:
Hostname=server1

Thanks



 Comments   
Comment by Oleksii Zagorskyi [ 2016 Jan 21 ]

Hard to understand is this about network discovery or agents auto-registration ...
I suppose there are existing similar discussions in this project.

Comment by Colum Flannigan [ 2016 Jan 21 ]

This is part of the Event source: Discovery section where it uses the network discovery to auto create hosts etc...
So instead of adding the host "server.example.com" you have the ability with a key_ to set just host "server1"

Comment by Aleksandrs Saveljevs [ 2016 May 05 ]

Similar request for SNMP items: ZBXNEXT-3266.

Comment by Arne Claerebout [ 2017 Nov 09 ]

This would defently be a handy feature when descovering devices that don't require a dns address, the ability to read an SNMP value or agent value and use that as the hostname would be perfect! Any news if this is in the pipeline?

Generated at Fri Apr 26 22:52:05 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.