[ZBXNEXT-437] Make the SNMP community string a attribute of a host Created: 2010 Jul 01 Updated: 2011 Dec 22 Resolved: 2011 Jan 14 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | None |
| Affects Version/s: | 1.8.2 |
| Fix Version/s: | 1.9.1 (alpha) |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Michael Schwartzkopff | Assignee: | Alexei Vladishev |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Description |
|
At the moment the SNMP community string is a attribute of every item. So if I enter 50 items for SNMP checks I have to enter 50 times the community string. Even worse: If I have servers of 50 customers to monitor and every customer has a different community string defined on his host I have to define 50 items for every of the 50 hosts. Or at least I do not see any way to a generic SNMP item that derives its way of authentication from the host data. Just imagine some hosts using SNMPv1, some v2c and some v3. Every time I define a new item basically for the same test. All this would be solved if the way to authenticate would be a attribute of a host, or better a host group, and the item inherits this attribute. Greetings, Michael |
| Comments |
| Comment by richlv [ 2010 Jul 02 ] |
|
this would most likely be solved by implementing user macro support for snmp community ( |
| Comment by richlv [ 2011 Jan 14 ] |
|
snmpv3 details will be handled in |
| Comment by Eugene Varnavsky [ 2011 Sep 17 ] |
|
Probably macro support in item configuration is a bit different thing, because it will require mass modification of items anyway. The issue is clear - there are different hosts with different community names and different SNMP protocol versions, so it would be wise to be able to set up community string and SNMP version on per-host basis, not per-item basis. The situation when different items in same host are accessed via different community names is impossible, as there is only one community name per host. But situation where you have different community names or protocol versions for different hosts is usual. As it is impossible to set community name or SNMP protocol version in host configuration, I currently use different templates, that have same set of items and differ only by community name. |