[ 
https://issues.apache.org/jira/browse/AMBARI-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946960#comment-14946960
 ] 

Hadoop QA commented on AMBARI-13205:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12765387/AMBARI-13205_2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3917//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3917//console

This message is automatically generated.

> 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
>             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)

Reply via email to