[AMBARI-16129] LogSearch Integration using incorrect query parameters for LogSearch

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Bob Nettleton
• Reporter: Bob Nettleton
• Created: 26/Apr/16 19:09
• Updated: 27/Apr/16 17:44
• Resolved: 27/Apr/16 15:41

Description

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.

Issue Links

• links to: ReviewBoard