ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18833) Add Support For Self-Contained Ambari SNMP
Date Wed, 09 Nov 2016 22:52:58 GMT


Hadoop QA commented on AMBARI-18833:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {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 ambari-server.

Test results:
Console output:

This message is automatically generated.

> Add Support For Self-Contained Ambari SNMP
> ------------------------------------------
>                 Key: AMBARI-18833
>                 URL:
>             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_3.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:
> The known Ambari OIDs are defined at:
> -
> 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

View raw message