[ZBXNEXT-158] ability to use discovery returned string as hostname Created: 2009 Dec 08  Updated: 2019 Jul 10  Resolved: 2019 Jul 05

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 4.2.0rc1, 4.2 (plan)

Type: New Feature Request Priority: Major
Reporter: richlv Assignee: Andrejs Kozlovs
Resolution: Fixed Votes: 74
Labels: discovery, flexibility
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PDF File ACC - Discovery - ability to use returned string as hostname - ZBXNEXT-158 - v1.0.pdf    
Issue Links:
Duplicate
Sub-task
depends on ZBXNEXT-4938 Frontend changes to ability to use di... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-4938 Frontend changes to ability to use di... Change Request (Sub-task) Closed Vasily Goncharenko  
Team: Team A
Sprint: Sprint 46, Nov 2018, Sprint 47, Dec 2018, Sprint 48, Jan 2019, Sprint 49 (Feb 2019), Sprint 50 (Mar 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
Story Points: 3

 Description   

even though discovery can now distinguish hosts with multiple interfaces and there's uniquity option, hosts are still added with their ips as hostnames.

it would be nice to add an option to add a host using returned string as hostname - this would be especially useful for various snmp devices where some snmp oid often contains useful string.

if the returned string contains characters that are not allowed in a hostname, they are replaced with underscores



 Comments   
Comment by Anclrej Keen [ 2012 Jun 03 ]

I'm surprised that this feature didn't appear in the 2.0 release. Snmp devices support is also important.
The way I see it, certain item should populate one special inventory field that works like "Visible name" field, or even replaces it. If the field is empty, IP is visible in the frontend.

Comment by Jori Hämäläinen [ 2012 Jun 08 ]

+1 for the last comment. It is sad that Zabbix cannot implement most obvious feature needed like allow population of hostname by sysName.0 from SNMP query.

Also visible hostname for maps should be allowed to be macro/regexp like dropping domain part out of hostname.

Comment by Jon [ 2012 Sep 03 ]

+1 Agreed

Comment by richlv [ 2012 Sep 03 ]

please see https://zabbix.org/wiki/Docs/bug_reporting_guidelines
notably the stuff about voting

Comment by viktorkho [ 2013 Jul 22 ]

+1 to issue

and my proposition:
Use 'returned string as' any macro's value? e.g., in

{HOST.DNS}

or

{HOSTNAME}

or

{USERMACRO}

with SNMP ".1.3.6.1.2.1.1.1.0" OID's value

Comment by Filipe Paternot [ 2013 Dec 10 ]

+1

It would be very useful to give hostname with sysName.0, specially with discovery + actions.

Comment by Ivan Kolomiets [ 2016 Feb 12 ]

+1 - tired of renaming discovered hosts

Comment by Dan [ 2016 Feb 13 ]

++ Need this feature 2

Comment by Mikhail Gladiy [ 2016 Feb 13 ]

+1

Comment by richlv [ 2016 Feb 14 ]

please read http://zabbix.org/wiki/Docs/bug_reporting_guidelines#Reporting_an_issue - particularly the section on voting

Comment by Adam Smith [ 2016 Mar 05 ]

I'm surprised this didn't make it into 3.0 with how long it has been open

Comment by Petr Fyodorov [ 2016 May 25 ]

As workaround
you can add PTR records to DNS so Zabbix will add discovered hosts with FQDN as hostname. It works for 3.0.2
Or
you can fill records to /etc/hosts at zabbix server. It works for 3.0.2 too

I have expected that Zabbix will use Hostname option in zabbix-agentd.conf or system hostname.

Comment by Håkan Franzen [ 2016 Oct 18 ]

Please fix this, I read alot about this and still no a solution or fix.
I have like 200 switchs that I need to add with autodiscovery and need to set hostname from SNMP.

The workaround is not a workaround, it as much job as entering all this manually.

Comment by Victor Hugo Assunção [ 2016 Nov 14 ]

Workaround... snmpget on sysname and mysql update:
https://github.com/victorhugopa/zabbix-scripts/blob/master/hostname_from_snmp.sh

Comment by Jori Hämäläinen [ 2017 May 29 ]

Above workaround (snmpwalk & mysql) does not work when monitoring with proxy. Because main server cannot snmpquery the host.

Much better option would be searching via HTTP API sysName-item(s) of hosts and check against host name. If not the same update. If same = be happy.

Comment by richlv [ 2017 May 29 ]

jhgrc, you can make it working through a proxy - for example, by sending the value to a trapper item on that host - but it is very hackish, of course.

Comment by Kevin Elmore [ 2017 Sep 26 ]

$50 to whoever adds this feature.

Comment by Rostislav Palivoda [ 2017 Sep 28 ]

If you really interested, then please check this https://www.zabbix.com/development_services or contact [email protected]

Comment by Ben Warfield [ 2017 Dec 15 ]

This request has been open for 8 years. How has this not been added? It's a simple request.

Comment by richlv [ 2017 Dec 15 ]

Ben, there are many, many requests and this is just one among them. providing patches or financing the development could speed this up

Comment by Petr Fyodorov [ 2017 Dec 15 ]

Could you collect donates for similar requests?

Comment by Rostislav Palivoda [ 2018 Aug 27 ]

No, we do not collect donations. I see 2 options to add feature in to the release road-map:

1) Signup for Enterprise service level and propose feature acceptance criteria to Zabbix Product Owner. In that option you can negotiate on acceptance criteria for the feature and make it more suitable for exactly your use case. 

2) Collect votes on the feature - in each release few top voted features selected for the development. 

Comment by Alexei Vladishev [ 2018 Nov 12 ]

This functionality will be implemented in Zabbix 4.2. Please have a look at the attached acceptance criteria (AC) document to see how it is going to be implemented and give us your feedback.

Comment by BenjaminG [ 2018 Nov 12 ]

@Alexei Vladishev Thanks a lot for this! I am happy with the AC. A bonus would be if you could use basic functions like string manipulations in Macros, to nicen up some things.

Comment by Kevin Elmore [ 2018 Nov 12 ]

Good news! I too think the AC looks good. I do have a question that I'm not sure applies. If the hosts are re-discovered at a later date, will the host name field auto-update as well? Or will this only work on initial discovery?

Comment by Andrejs Kozlovs [ 2019 Mar 04 ]

Fixed in:

  • pre-4.2.0beta2 (trunk) 90527
Comment by Alexander Vladishev [ 2019 Jul 05 ]

Updated general documentation:

Comment by Kevin Elmore [ 2019 Jul 10 ]

Thanks for all the hard work on this feature. It is really nice to have. 

As I was working to implement this new feature, I stumbled on a new idea. Could the hostname Oid Value be dependent on results from another one of the oid value checks?

This is important for the situation where a discovery scan block is used to discover many different types of devices. Maybe the devices only support v1 and not v2 snmp, which means only some of the devices will get named that are discovered in a particular discovery scan. One option would be to use a priority...so that the first one that responds is used for the host name. Another option could be adding some logic to the discovery settings that allow the user to select a host name oid based on a result from another check.

 

Another way to resolve this would be allowing the host name to be set or updated during the Action phase, after discovery has happened. I appreciate adding this capability, and I can make this work by having two different discoveries set up, dependent on the devices I am looking for, but I figured I would bring this up now while it is a freshly implemented feature. Maybe what I am asking for needs to be a whole new feature request as well. Thanks!

Generated at Fri Mar 29 03:15:58 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.