[jira] [Updated] (AMBARI-18161) Support UNKNOWN log level for Log Search

["Olivér Szabó (JIRA)" <ji...@apache.org>]

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

Olivér Szabó updated AMBARI-18161:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

committed to trunk:
{code:java}
commit 3fd1742b5d2e4ee901a210ff8b7ea1f0c5c5dc27
Author: oleewere <ol...@gmail.com>
Date:   Mon Aug 22 11:01:36 2016 +0200

    AMBARI-18161. Support UNKNOWN log level for Log Search (Dharmesh Makwana via oleewere)
{code}
comitted to branch-2.5:
{code:java}
commit 1ee15dc0ee7888be139f8f5745d831a9f58f617f
Author: oleewere <ol...@gmail.com>
Date:   Mon Aug 22 11:01:36 2016 +0200

    AMBARI-18161. Support UNKNOWN log level for Log Search (Dharmesh Makwana via oleewere)
{code}

> Support UNKNOWN log level for Log Search
> ----------------------------------------
>
>                 Key: AMBARI-18161
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18161
>             Project: Ambari
>          Issue Type: Improvement
>          Components: logsearch
>    Affects Versions: 2.4.0
>            Reporter: Dharmesh Makwana
>            Assignee: Dharmesh Makwana
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18161.patch
>
>
> In some cases, there are no log level inforamtion in logs, therefore we need to map the log to a log level, but that is maybe not the proper solution (e.g. we are mapping X log to INFO log level, but maybe a customer wants to see only error,warn,fatal level logs, because customer has too many INFO level logs..in that case logs only visible if INFO level filter is on)



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