You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2020/03/26 05:59:58 UTC

[GitHub] [skywalking] wu-sheng commented on issue #4572: some query and monitoring features

wu-sheng commented on issue #4572: some query and monitoring features
URL: https://github.com/apache/skywalking/issues/4572#issuecomment-604245928
 
 
   > 1、In our system, a request will have many redis queries; so in the tracking chain query interface, there will be many jedis records in the list. How to filter out these records and only display other related content。
   
   You could remove redis plugin.
   
   > 2、Can the apm agent track a thread with a high CPU usage and push an alarm event containing the thread-related traceId , via mq or other methods. In this way, we can monitor the event and limit the request resource corresponding to the traceId, or even the user request.
   
   1. CPU alert, yes, you could set the rule to cpu related metrics. 
   1. Trace id has nothing related to this. CPU is not thread-level metrics. I think you have wrong concept about the metrics and trace id relationship.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services