[
https://issues.apache.org/jira/browse/FLINK-17088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-17088:
----------------------------------
Priority: Minor (was: Critical)
> Search TaskManager log content based on keywords function
> ---------------------------------------------------------
>
> Key: FLINK-17088
> URL: https://issues.apache.org/jira/browse/FLINK-17088
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / REST, Runtime / Web Frontend
> Affects Versions: 1.10.0
> Reporter: pingle wang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Attachments: image-2020-04-11-01-30-09-551.png,
> image-2020-04-11-01-30-21-681.png, image-2020-04-11-01-30-38-046.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Usually the taskmanager log file has a lot of content. There are several ways
> to search for content keywords:
> The first one: in browser ctrl + f
> The second type: use shell command operations on the server ip, such as grep
> -A
> The third kind: Log files are connected to Elasticsearch through Logstash /
> Filebeat
> These all increase the user's operation, which brings inconvenience, so the
> search function is developed to query the log content.
> Description:
> 1. web input box word means search keyword, the default value is empty
> 2. The input box lines indicates how many lines follow the keyword,
> similar to 'grep -A 10 Exception', lines default value is 0.
> 3. If the search returns empty, display as 'No content matching the search
> keywords'
>
> Function display:
> !image-2020-04-11-01-30-09-551.png!
> !image-2020-04-11-01-30-21-681.png!
> !image-2020-04-11-01-30-38-046.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
