[
https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064936#comment-16064936
]
Miklos Gergely commented on AMBARI-21145:
-----------------------------------------
About the problem in the description:
In fact Log Feeder doesn't support wild card characters in the log folder
names. Our assumption was that if there are log files in separate folders the
users would surely don't want to load them under the same log id (called type
in the input configuration). So you can create a separate input elements for
each one of them, and they will be loaded each under their own log id. Please
confirm if you really want to load input files from different folders under the
same log id, and then we can take a look at the issue, but consider the
suggestions above.
About the problem in comment #1:
if the "tail" parameter is "true", then Log Feeder loads only the first file
found for a path with wildcard characters in it. If you set the "tail"
parameter to "false", then it will load all of them, but will also stop after
it loaded them i.e. it won't wait for new entries to come. We are planning to
modify this behavior, and make it possible to load all the files and follow the
first one. This is good for rolled over log files, where the user wants to load
all the previous parts, but only follow the actual one.
However if you still want to load log files from different directories, or
specify a path with wild card in it in order to track multiple active log
files, and follow all of them then it is not good.
> allow wildcard for log directory folder in the path component of Logfeeder
> input
> --------------------------------------------------------------------------------
>
> Key: AMBARI-21145
> URL: https://issues.apache.org/jira/browse/AMBARI-21145
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
> Affects Versions: 2.5.0
> Reporter: Keta Patel
> Assignee: Keta Patel
> Priority: Minor
>
> The wildcard processing in Logfeeder is carried out only for the last file
> component in the log path. For a few services, where there are multiple log
> folders and log files from each of the folders is desired to be parsed in
> Logsearch UI, the lack of a wildcard processing for the previous portions
> becomes an issue. Hence, introducing wildcard processing for the log
> directory part of the "path" in the Logfeeder's input for the service will
> help resolve this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)