If it is not tuned properly, custom rules can cause performance issues. Which tool allows you to troubleshoot if a rule causes performance issues?

Question

Options

• AthreadTop.sh
• BfindExpensiveCustomRules.sh
• CcollectGvStats.sh
• Dvalidate_ecs_service.sh

• A
  15% (9)
• B
  75% (45)
• C
  3% (2)
• D
  7% (4)

Explanation

findExpensiveCustomRules.sh is purpose-built to identify which custom rules are consuming excessive resources, making it the go-to diagnostic tool when rule tuning is suspected as a performance bottleneck. threadTop.sh (A) monitors thread-level CPU activity in a general sense - useful for spotting overloaded threads, but not specific to custom rule evaluation. collectGvStats.sh (C) gathers global variable statistics for memory/state analysis, not rule performance profiling. validate_ecs_service.sh (D) is an ECS service health/configuration validator, unrelated to rule performance troubleshooting entirely.

Memory tip: The script name tells you exactly what it does - "find expensive custom rules." When you see a performance question about custom rules, look for the script whose name literally describes the problem you're solving.

No community discussion yet for this question.