You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Olivér Szabó (JIRA)" <ji...@apache.org> on 2016/04/07 20:55:25 UTC

[jira] [Updated] (AMBARI-15679) Initial commit for LogSearch service definition

     [ https://issues.apache.org/jira/browse/AMBARI-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivér Szabó updated AMBARI-15679:
----------------------------------
    Attachment: 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ér Szabó
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15679.patch
>
>
> 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 services
> * Log search service that provides REST API and UI front end
> The above components are managed by Ambari through a stack definition. The stack definition provides the mechanism to have the LogSearch service configured to read log files created by other services, including Ambari Server. 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 service dashboards.



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