[
https://issues.apache.org/jira/browse/AMBARI-15139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-15139:
-----------------------------------
Description: Ambari already deploys a number of services and is aware of
the log file location for all the services. If there is a need to debug,
currently, user needs to go to each host and 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. (was:
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.)
> 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 is aware of the log file
> location for all the services. If there is a need to debug, currently, user
> needs to go to each host and 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)
