[ZBXNEXT-201] Required to implement autoregistration of the zabbix_agent using it's IP. Created: 2010 Jan 11 Updated: 2015 Nov 20 Resolved: 2011 Mar 24 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 1.8.3 |
| Fix Version/s: | 1.9.1 (alpha) |
| Type: | Change Request | Priority: | Major |
| Reporter: | Igor Danoshaites (Inactive) | Assignee: | Alexander Vladishev |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix v1.8.x |
||
| Issue Links: |
|
||||
| Description |
|
Autoregistration of the zabbix_agent. When zabbix_agents are registered using autoregistration by default they are set to connect to "DNS name" and using IP=127.0.0.1. |
| Comments |
| Comment by richlv [ 2010 Jan 11 ] |
|
also discussed in http://www.zabbix.com/forum/showthread.php?t=15039 |
| Comment by Jan Vilhuber [ 2010 Mar 29 ] |
|
This is a high priority issue, since in EC2 the hostnames are not terribly useful in identifying a machine for our purposes. In order to reasonably be able to manage the machines, we need to be able to set an alias as the hostname that means something to us, but is not a hostname. The IP address should be gotten from the incoming connection and automatically set. Any plans to get this in soonest? |
| Comment by Alexander Fedulov [ 2010 Nov 02 ] |
|
This is a crucial issue for us as well, as we currently estimate Zabbix as a candidate for monitoring solution in a big project, related to Cloud Computing. The ability to correctly register newly instantiated VMs with their real IP addresses is essential. Is this issue expected to be solved in the near future? |
| Comment by Gavin Brown [ 2011 Mar 24 ] |
|
Please see the following for patch files for a "quick" fix (still WIP). |
| Comment by richlv [ 2011 Mar 24 ] |
|
i believe this was implemented as |