[
https://issues.apache.org/jira/browse/AMBARI-15613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-15613:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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)
