Class NoopDiagnosticCallStackFlushStrategy
java.lang.Object
io.higson.runtime.profiler.callstack.NoopDiagnosticCallStackFlushStrategy
- All Implemented Interfaces:
DiagnosticCallStackFlushStrategy
public class NoopDiagnosticCallStackFlushStrategy
extends Object
implements DiagnosticCallStackFlushStrategy
Tester
DiagnosticCallStackFlushStrategy: does nothing on flush.
Used by the tester path (wired in the core module's Spring context monitor) so that the
thread-local DiagnosticCallStack is preserved after the engine/interceptor finishes
its top-level frame. The tester reads the stack directly in
DiagnosticParamService#stopDiagnostic and clears it there.
Does NOT clear the stack — that is intentional and part of the strategy contract.
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidflush(String elementName, DiagnosticCallStackEvent.ElementType elementType, DiagnosticCallStackSummary summary, String instanceId) Called once the top-level profiling frame has finished.
-
Constructor Details
-
NoopDiagnosticCallStackFlushStrategy
public NoopDiagnosticCallStackFlushStrategy()
-
-
Method Details
-
flush
public void flush(String elementName, DiagnosticCallStackEvent.ElementType elementType, DiagnosticCallStackSummary summary, String instanceId) Description copied from interface:DiagnosticCallStackFlushStrategyCalled once the top-level profiling frame has finished.- Specified by:
flushin interfaceDiagnosticCallStackFlushStrategy- Parameters:
elementName- name of the top-level element (parameter / function / flow / attribute path)elementType- type of the top-level elementsummary- aggregated call-stack summary generated from the current thread-local stackinstanceId- identifier of the runtime engine instance that produced the report
-