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 2016/04/26 21:10:12 UTC

[jira] [Created] (AMBARI-16129) LogSearch Integration using incorrect query parameters for LogSearch

Robert Nettleton created AMBARI-16129:
-----------------------------------------

             Summary: LogSearch Integration using incorrect query parameters for LogSearch
                 Key: AMBARI-16129
                 URL: https://issues.apache.org/jira/browse/AMBARI-16129
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
            Priority: Critical
             Fix For: 2.4.0


The LogSearch integration layer in Ambari is passing incorrect query parameters to the LogSearch Server.  Recent multi-node testing has uncovered this issue. 

The LogSearch integration code should use "host_name" for specifying hosts in query URLs, and "component_name" for specifying the component for a given LogSearch query.  The "component_name" change is related to a change in the parameters for LogSearch itself, which used to use "components_name".  

The integration code should be updated to use these query parameter names.  

I'm working on a fix for this, and will be submitting a patch shortly. 




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