Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0F33B200CD3 for ; Fri, 28 Jul 2017 15:06:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0DD1816762D; Fri, 28 Jul 2017 13:06:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 53A74169B67 for ; Fri, 28 Jul 2017 15:06:03 +0200 (CEST) Received: (qmail 58963 invoked by uid 500); 28 Jul 2017 13:06:02 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 58954 invoked by uid 99); 28 Jul 2017 13:06:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Jul 2017 13:06:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1A8C6C3649 for ; Fri, 28 Jul 2017 13:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id TsEryT38q-ZB for ; Fri, 28 Jul 2017 13:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F1DCC5FD41 for ; Fri, 28 Jul 2017 13:06:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 89FBFE0DA4 for ; Fri, 28 Jul 2017 13:06:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3A61124D27 for ; Fri, 28 Jul 2017 13:06:00 +0000 (UTC) Date: Fri, 28 Jul 2017 13:06:00 +0000 (UTC) From: "Hari Sekhon (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-21597) Document Ambari Alert checks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 28 Jul 2017 13:06:04 -0000 Hari Sekhon created AMBARI-21597: ------------------------------------ Summary: Document Ambari Alert checks Key: AMBARI-21597 URL: https://issues.apache.org/jira/browse/AMBARI-21597 Project: Ambari Issue Type: New Feature Components: documentation Affects Versions: 2.5.1 Environment: HDP 2.6 / HDF 3.0 + Kerberos Reporter: Hari Sekhon Request to add online documentation listing all Ambari Alerts checks, script locations and description around what each one does. You can get most of this information from an Ambari instance's Alerts section, but I think this should still be documented online so that people can see this information if they don't have an Ambari instance available. This will allow one to see what is and isn't covered at any time, which is useful when advising on what additional enterprising monitoring to supplement or when raising requests for additional Ambari checks by cross checking what is already there. -- This message was sent by Atlassian JIRA (v6.4.14#64029)