[
https://issues.apache.org/jira/browse/AMBARI-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948925#comment-14948925
]
Hudson commented on AMBARI-13205:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3615 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3615/])
AMBARI-13205 SNMP MIB for Alerts (Paul Codding via dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=77281dd5826ce8860c26c8b79b3afe5e30832414])
* contrib/alert-snmp-mib/snmp_mib_script.sh
* contrib/alert-snmp-mib/README.md
* contrib/alert-snmp-mib/APACHE-AMBARI-MIB.txt
> SNMP MIB for Alerts
> -------------------
>
> Key: AMBARI-13205
> URL: https://issues.apache.org/jira/browse/AMBARI-13205
> Project: Ambari
> Issue Type: Improvement
> Components: alerts
> Affects Versions: 2.1.0
> Reporter: Paul Codding
> Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13205.patch, AMBARI-13205_2.patch,
> APACHE-AMBARI-MIB.txt, README.md, snmp_mib_script.sh
>
>
> Operations teams expect Ambari to have a MIB that defines the superset of
> OID’s that will be in use and their context. In this context, Ambari will
> not be exposing any SNMP metrics, but only emitting SNMP traps from the
> alerting framework.
> Those SNMP traps that are emitted need to send traps for specific OID’s.
> Those OID’s should be defined in a MIB.
> That MIB should be followed when sending traps for specific alerts. The
> specific alerts should send traps with specific OID’s that apply to their
> context.
> For now a MIB, a script extension and documentation to apply that to an
> existing Ambari 2.1 environment are sufficient.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
