You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Istvan Tobias (JIRA)" <ji...@apache.org> on 2018/06/04 15:17:00 UTC

[jira] [Assigned] (AMBARI-24005) [Logsearch UI] "Open log" context menu navigates user to default 'last 1 hour' filtered logs

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

Istvan Tobias reassigned AMBARI-24005:
--------------------------------------

    Assignee: Istvan Tobias

> [Logsearch UI] "Open log" context menu navigates user to default 'last 1 hour' filtered logs
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24005
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24005
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 2.7.0
>            Reporter: Kishor Ramakrishnan
>            Assignee: Istvan Tobias
>            Priority: Major
>             Fix For: 2.7.0
>
>
> "Open log" context menu navigates user to default 'last 1 hour' filtered logs
> STR:
> 1. Login to logsearch portal
> 2. Select a valid time range with logs available for a specific component (e.g ambari-server for last 3 hours)
> 3. Pick one specific log row from the log table and click context menu and click open log, and the user should be navigated to the newly opened logsearch tab with the selected log highlighted and with the same filtered time window chosen by the user.
> 4. But the user is navigated to a new tab with custom filter of last one 1 hour and the user may not find the log he/she selected in the previous tab unless the log belongs in the last 1-hour window.
> Note:
> Also observed that when the user closes the newly opened tab with the custom filter, the previously searched 'Service Logs' tab also has the filter set as the custom tab (i.e 'Last 1 hour' and the component selected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)