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

Posted to issues@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2017/04/25 18:35:04 UTC

[jira] [Resolved] (AMBARI-20845) Include cluster filter in every Log Search request in Ambari server

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

Robert Nettleton resolved AMBARI-20845.
---------------------------------------
    Resolution: Fixed

Patch merged to trunk and branch-2.5

> Include cluster filter in every Log Search request in Ambari server
> -------------------------------------------------------------------
>
>                 Key: AMBARI-20845
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20845
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.1
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.5.1
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The Ambari LogSearch integration layer should be updated to pass the name of the current cluster to the LogSearch Portal Server when requesting either Logging component metadata or when making a query request for logging data itself.
> In Ambari 2.5.1, the LogSearch service has been updated to potentially archive data from multiple clusters.  The Ambari Integration layer should be updated to reflect this, in order to indicate to LogSearch what cluster's data is requested, since Ambari only will require the currently managed cluster's log data. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)