You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Miklos Gergely (JIRA)" <ji...@apache.org> on 2016/06/16 13:20:05 UTC

[jira] [Updated] (AMBARI-17277) Log Level filter not applied before Log Search Starts at first

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

Miklos Gergely updated AMBARI-17277:
------------------------------------
    Status: Patch Available  (was: In Progress)

> Log Level filter not applied before Log Search Starts at first
> --------------------------------------------------------------
>
>                 Key: AMBARI-17277
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17277
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 2.4.0
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17277.patch
>
>
> After Log Search is started it sends the filters to the Solr which describes what log levels should be persisted. In the meantime Logfeeders start to push their data, which is not filtered. The result is misleading, the user may find it add that some specific level logs are loaded, others are not.



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