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 2018/06/25 23:15:00 UTC
[jira] [Updated] (AMBARI-24183) Log Feeder: read docker container
logs
[ https://issues.apache.org/jira/browse/AMBARI-24183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivér Szabó updated AMBARI-24183:
----------------------------------
Description:
- implement a container registry which can update / gather docker metadata for logfeeder (like actual container log path etc.)
- new field in input configuration: "docker", e.g.:
{code:java}
"inputs" : [
{
...
"docker" : "true"
}
{code}
If this value is set to `true`, then for every line a json pattern should be applied first (before go with anything else like grok filters)
> Log Feeder: read docker container logs
> --------------------------------------
>
> Key: AMBARI-24183
> URL: https://issues.apache.org/jira/browse/AMBARI-24183
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 3.0.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Major
> Fix For: 3.0.0
>
>
> - implement a container registry which can update / gather docker metadata for logfeeder (like actual container log path etc.)
> - new field in input configuration: "docker", e.g.:
> {code:java}
> "inputs" : [
> {
> ...
> "docker" : "true"
> }
> {code}
> If this value is set to `true`, then for every line a json pattern should be applied first (before go with anything else like grok filters)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)