[
https://issues.apache.org/jira/browse/AMBARI-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162852#comment-16162852
]
Hadoop QA commented on AMBARI-21922:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12886441/AMBARI-21922.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12182//console
This message is automatically generated.
> Allow SERVER Type Alerts To Run For Any Service/Component
> ---------------------------------------------------------
>
> Key: AMBARI-21922
> URL: https://issues.apache.org/jira/browse/AMBARI-21922
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Fix For: 3.0.0, 2.6.0
>
> Attachments: AMBARI-21922.patch
>
>
> There is a type of alert known as a "SERVER" alert which is a Java class that
> runs inside of the Ambari Server. We use these alerts to check for specific
> issues with the Ambari Server itself.
> However, nothing should prevent a cluster's services from being able to
> define one of these. Consider the following case where we want a new
> server-side alert to run for the ZooKeeper Service which checks something
> specific that none of the agent-side alerts are appropriate for:
> {code}
> {
> "ZOOKEEPER": {
> "service": [
> {
> "name": "Foo",
> "label": "Foo ZK Alert",
> "description": "Foo",
> "interval": 5,
> "scope": "SERVICE",
> "enabled": true,
> "source": {
> "type": "SERVER",
> "class": "org.apache.ambari.server.alerts.ZKFooChecker"
> }
> }
> ],
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
