[
https://issues.apache.org/jira/browse/HDDS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDDS-2071:
-----------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks [~elek] for the contribution. I've merged the fix to master.
> Support filters in ozone insight point
> --------------------------------------
>
> Key: HDDS-2071
> URL: https://issues.apache.org/jira/browse/HDDS-2071
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> With Ozone insight we can print out all the logs / metrics of one specific
> component s (eg. scm.node-manager or scm.node-manager).
> It would be great to support additional filtering capabilities where the
> output is filtered based on specific keys.
> For example to print out all of the logs related to one datanode or related
> to one type of RPC request.
> Filter should be a key value map (eg. --filter
> datanode=sjdhfhf,rpc=createChunk) which can be defined in the ozone insight
> CLI.
> As we have no option to add additional tags to the logs (it may be supported
> by log4j2 but not with slf4k), the first implementation can be implemented by
> pattern matching.
> For example in SCMNodeManager.processNodeReport contains trace/debug logs
> which includes the " [datanode={}]" part. This formatting convention can be
> used to print out the only the related information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
