You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (Jira)" <ji...@apache.org> on 2020/05/18 03:00:06 UTC

[jira] [Commented] (ATLAS-514) Monitoring and alerts for HA

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

Madhan Neethiraj commented on ATLAS-514:
----------------------------------------

[~sidharthkmishra], [~sarath] - consider adding HA events to admin audits introduced in ATLAS-3518.

> Monitoring and alerts for HA
> ----------------------------
>
>                 Key: ATLAS-514
>                 URL: https://issues.apache.org/jira/browse/ATLAS-514
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Hemanth Yamijala
>            Priority: Major
>
> This JIRA is to capture any requirements that allow admins and users to determine if there are any interesting events related to HA of the Atlas Server, such as:
> * All events related to HA of the Atlas server must be audited, including becoming an active instance, manual failovers, error scenarios in HA etc.
> * An HA setup of Atlas must detect if any dependent component (HBase, Solr, Kafka) is in non-HA configuration, and if yes, it must log an audit event.
> * If an HA setup of Atlas is unable to use a dependent HA component (HBase, Solr, Kafka) it must log an audit event.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)