{"tool":"trace","tool_display":"Trace","intent":"trace-multiple-classes-or-methods","intent_display":"trace multiple classes or methods","title":"Trace Command: trace multiple classes or methods","command_string":"trace -E <class-pattern1>|<class-pattern2> <method-pattern1>|<method-pattern2>|<method-pattern3>","raw_command_string":"trace -E {{class-pattern1}}|{{class-pattern2}} {{method-pattern1}}|{{method-pattern2}}|{{method-pattern3}}","description":"Exact CLI syntax to trace multiple classes or methods using Trace.","usage_scenario":"Deploy this command in high-load environments where specific classes or methods are suspected as bottlenecks. It is especially crucial when traditional logging adds too much overhead or when intermittent issues occur, making reproducing them challenging.","scenario_context":"Optimize performance by tracing specific methods during peak loads without excessive overhead.","simulated_output":"Tracing started for patterns:\n\n┌───────────────────────┬───────────────────────┐\n│ Class Pattern         │ Method Pattern        │\n├───────────────────────┼───────────────────────┤\n│ com.example.ClassOne  │ methodOne            │\n│ com.example.ClassTwo  │ methodTwo            │\n│                       │ methodThree          │\n└───────────────────────┴───────────────────────┘\n\nTracing... Done.\n\nResults stored in /var/log/trace_results.log","how_to_steps":["Run the command: `trace -E com\\.example\\.ClassOne|com\\.example\\.ClassTwo methodOne|methodTwo|methodThree`","Check for output in: `/var/log/trace_results.log`","Analyze the captured trace data for performance issues."],"inferred_category":"Observability","canonical_url":"https://www.syntaxstandard.com/trace/trace-multiple-classes-or-methods"}