Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5658B191AB for ; Thu, 7 Apr 2016 20:00:28 +0000 (UTC) Received: (qmail 75536 invoked by uid 500); 7 Apr 2016 20:00:28 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 75468 invoked by uid 500); 7 Apr 2016 20:00:28 -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 75444 invoked by uid 99); 7 Apr 2016 20:00:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Apr 2016 20:00:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D53382C1F64 for ; Thu, 7 Apr 2016 20:00:27 +0000 (UTC) Date: Thu, 7 Apr 2016 20:00:27 +0000 (UTC) From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15679?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliv=C3=A9r Szab=C3=B3 updated AMBARI-15679: ---------------------------------- Attachment: (was: AMBARI-15679.patch) > Initial commit for LogSearch service definition > ----------------------------------------------- > > Key: AMBARI-15679 > URL: https://issues.apache.org/jira/browse/AMBARI-15679 > Project: Ambari > Issue Type: Technical task > Components: stacks > Affects Versions: 2.4.0 > Reporter: Sumit Mohanty > Assignee: Oliv=C3=A9r Szab=C3=B3 > Fix For: 2.4.0 > > > LogSearch service includes three major components: > * A Solr cloud to store logs and query > * Log collectors/feeders that consume log files being generated by the se= rvices > * Log search service that provides REST API and UI front end > The above components are managed by Ambari through a stack definition. Th= e stack definition provides the mechanism to have the LogSearch service con= figured to read log files created by other services, including Ambari Serve= r. This integration allows customizing log locations and letting LogSearch = service be aware of the locations. > Final peace is to provide an integration from the Ambari UI to LogSearch = service so that the logs for a service is easily accessible from the servic= e dashboards. -- This message was sent by Atlassian JIRA (v6.3.4#6332)