[
https://issues.apache.org/jira/browse/AMBARI-18833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651080#comment-15651080
]
Dmytro Sen commented on AMBARI-18833:
-------------------------------------
Failed python tests aren't related to the patch
> Add Support For Self-Contained Ambari SNMP
> ------------------------------------------
>
> Key: AMBARI-18833
> URL: https://issues.apache.org/jira/browse/AMBARI-18833
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-server
> Affects Versions: 2.5.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18833.patch
>
>
> Currently, Ambari's {{SNMP}} alert target type is using to bind generic OIDs
> specified by the administrator when creating the target. Many users would
> rather that Ambari provide a MIB which can then be imported into their
> management tool and just use the pre-defined OIDs.
> Ambari has applied for and received OIDs from Apache which are included in
> our MIB file. The MIB is located at:
> https://github.com/apache/ambari/blob/trunk/contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
> The known Ambari OIDs are defined at:
> https://cwiki.apache.org/confluence/display/DIRxPMGT/OID+Assignment+Scheme
> - 1.3.6.1.4.1.18060.16
> A new alert target type of {{AMBARI_SNMP}} should be created which knows
> about the pre-existing OIDs so that dispatching SNMP traps to this type are
> correctly bound automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
