ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Attila Magyar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21922) Allow SERVER Type Alerts To Run For Any Service/Component
Date Tue, 12 Sep 2017 11:16:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Attila Magyar updated AMBARI-21922:
-----------------------------------
    Status: Patch Available  (was: Open)

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

Mime
View raw message