[ZBXNEXT-2679] automatic add the user macro {$SNMP_COMMUNITY} in discovery of SNMP OIDs Created: 2015 Jan 23  Updated: 2017 May 31

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

Type: Change Request Priority: Minor
Reporter: cheliequan Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: discovery, macros, networkdiscovery, patch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 2.6.32-504.el6.x86_64 #1 SMP Wed Oct 15 04:27:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


Attachments: PNG File 2015-01-28_142613.png     PNG File 2015-01-28_142717.png     PNG File 2015-01-28_142735.png     PNG File 2015-01-28_143013.png     PNG File 2015-01-28_150759.png     Text File action_c.patch     Text File actions.c     Text File operations.c     Text File operations.h     Text File operations_c.patch     Text File operations_h.patch     Zip Archive zabbix_server-auto-add-macro-in-discover-patch.zip    

 Description   

In Discovery action, the Action operations do not support add the user macro such as ${SNMP_COMMUNITY}?
It cannot automatically collect through SNMP-based data collection method in discovery?
It happens when the snmp community is not default value that is public.
The Patch only support SNMP V1/V2 now?SNMP V3 is not supported..Even
If someone needs the feture support SNMPV3 is is easy to accomplish?



 Comments   
Comment by richlv [ 2015 Jan 23 ]

if i got the idea right, couldn't this be achieved by having a template with the correct macro, then linking it in the discovery ?

Comment by cheliequan [ 2015 Jan 24 ]

yes,you are right.there is no need to add user macro manually when the user macro about {$SNMP_COMMUNITY} is not public.It means someone just need one attempt to add the snmp community in the snmp check rule.

Comment by richlv [ 2015 Jan 26 ]

could you please clarify whether the suggested approach (templates with macros) solves this issue or not ?

Comment by cheliequan [ 2015 Jan 26 ]

the patch slove the problem now.I have tested it in my test environment.

Comment by cheliequan [ 2015 Jan 28 ]

step to trigger the bug

Comment by cheliequan [ 2015 Mar 15 ]

code optimize

Generated at Thu Apr 25 10:35:35 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.