[jira] [Resolved] (AMBARI-23445) Refactor metrics_alert to support multiple nameservices

["Endre Major (JIRA)" <ji...@apache.org>]

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

Endre Major resolved AMBARI-23445.
----------------------------------
    Resolution: Fixed

> Refactor metrics_alert to support multiple nameservices
> -------------------------------------------------------
>
>                 Key: AMBARI-23445
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23445
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Endre Major
>            Assignee: Endre Major
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The HDFS metrics based alerts defined in alert_metrics_deviation.py is agnostic of federated Namenodes.
> Tasks:
> When federation is enabled we should add an alert instance per nameservice for the HDFS metric based alerts.
> Currently, we track metrics based alerts for:
> RPC processing latency
> RPC queue latency
> NN Heap usage
> There are multiple alerts based on whether service port is enabled and also different time windows. 
> For every alert type, there should be an instance of the alert per nameservice.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)