Return-Path: 
 <issues-return-3015-apmail-ambari-issues-archive=ambari.apache.org@ambari.apache.org>
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 C56C9195D7
	for <apmail-ambari-issues-archive@minotaur.apache.org>;
 Wed, 30 Mar 2016 08:09:25 +0000 (UTC)
Received: (qmail 57436 invoked by uid 500); 30 Mar 2016 08:09:25 -0000
Delivered-To: apmail-ambari-issues-archive@ambari.apache.org
Received: (qmail 57404 invoked by uid 500); 30 Mar 2016 08:09:25 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 57393 invoked by uid 99); 30 Mar 2016 08:09:25 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2016 08:09:25 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 702FE2C0452
	for <issues@ambari.apache.org>; Wed, 30 Mar 2016 08:09:25 +0000 (UTC)
Date: Wed, 30 Mar 2016 08:09:25 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12954246.1459244861000.86024.1459325365455@Atlassian.JIRA>
In-Reply-To: <JIRA.12954246.1459244861000@Atlassian.JIRA>
References: <JIRA.12954246.1459244861000@Atlassian.JIRA>
 <JIRA.12954246.1459244861981@arcas>
Subject: [jira] [Commented] (AMBARI-15613) Provide a mapping for
 service/component to log ID
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hadoop QA commented on AMBARI-15613:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12795953/AMBARI-15613.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6089//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6089//console

This message is automatically generated.

> Provide a mapping for service/component to log ID	
> --------------------------------------------------
>
>                 Key: AMBARI-15613
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15613
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15613.patch
>
>
> Add of logfile IDs to the metainfo.xml files to support the upcoming logsearch service. These ids are the identifier to each log collections and represent a log file on disk. Ambari APIs need the ability to map the IDs to the actual service/component as well.
> Example:
> {code}
> <component>
>   <name>HBASE_MASTER</name>
>   <displayName>HBase Master</displayName>
>   <category>MASTER</category>
>   <cardinality>1+</cardinality>
>   <versionAdvertised>true</versionAdvertised>
>   <timelineAppid>HBASE</timelineAppid>
>   <logs>
>     <log>
>       <logId>hbase_master</logId>
>     </log>
>   </logs>
>   ...
> </component>
> {code}
> A component can have more than one logId - e.g. AMS Collector.
> Eventually <log>...</log> can contain other metadata such as log type (regular or audit), the link to the log feeder configuration, etc.



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