[
https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857972#comment-15857972
]
Miklos Gergely commented on AMBARI-19906:
-----------------------------------------
Generally I think it's a great new functionality, though I don't believe that
we should save it to HDFS. Instead I'd suggest to limit the number of log
entries that may be returned this way, i.e. the portal would first check the
number of log entries involved, and send an error message if it's over the
limit. Otherwise the tar file could be generated in a local directory, and
could be downloaded from there. After a pre-set time the tar files would be
deleted.
> Ambari Log Search – Single Click Log Collection and Download.
> -------------------------------------------------------------
>
> Key: AMBARI-19906
> URL: https://issues.apache.org/jira/browse/AMBARI-19906
> Project: Ambari
> Issue Type: Story
> Components: ambari-logsearch, logsearch
> Affects Versions: 2.4.0, 2.4.2
> Reporter: George Mathew
> Assignee: George Mathew
> Fix For: trunk
>
> Attachments: Proposal.pdf
>
>
> Ambari Log Search can be used to download log messages for further analysis.
> It lets you download log messages generated by a specific service in a
> specific node in the cluster.
> The challenge comes when troubleshooting several services spanning several
> nodes and you want to collect all the logs, there is no simple way to click
> and collect them at once. I am proposing a solution that would simplify the
> current actions needed to collect logs by clicking a button. The proposed
> download button will collect all the logs in the search criteria, organize
> them by service, place them on HDFS and offer a download link
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
