Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 23 Feb 2016 04:48:18 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12941274.1456202853000.117488.1456202898072@Atlassian.JIRA>
In-Reply-To: <JIRA.12941274.1456202853000@Atlassian.JIRA>
References: <JIRA.12941274.1456202853000@Atlassian.JIRA>
 <JIRA.12941274.1456202853641@arcas>
Subject: [jira] [Created] (AMBARI-15139) Tracks work items related to log
 accumulation and searching support in Ambari
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sumit Mohanty created AMBARI-15139:
--------------------------------------

             Summary: Tracks work items related to log accumulation and searching support in Ambari
                 Key: AMBARI-15139
                 URL: https://issues.apache.org/jira/browse/AMBARI-15139
             Project: Ambari
          Issue Type: Epic
          Components: stacks
    Affects Versions: 2.2.2
            Reporter: Sumit Mohanty
            Assignee: Sumit Mohanty
            Priority: Critical
             Fix For: 2.4.0


Ambari already deploys a number of services and know of the log location for all the services. Currently, user needs to go to each host to look up for log files  and manually browse through each file to debug issues. This can be greatly improved by creating a log search service (a stack service in itself) that can be configured to ingest existing log files and allowing easy search/query across all log files - include Ambari's own.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)