Portal Community

Level Filter Chips

All
Debug
Info
Warning
Error
Critical

Level Hierarchy

The level filter is not hierarchical — selecting "Error" does not automatically include "Critical". Each chip is an exact-match toggle. Multiple chips can be active simultaneously:

Filter Implementation

// Level filter applied to the log buffer
const visibleLogs = logs.filter(entry =>
  selectedLevels.size === 0           // "All" selected
  || selectedLevels.has(entry.level)  // specific level selected
);

Recommended Filter Combinations

ScenarioSelect
Execution failed — find the causeError + Critical
Performance investigationInfo (most executors log timing at Info level)
Debugging a specific nodeAll + set Node filter to that node
Verbose trace of entire executionAll (default)
Ignore noise, see only problemsWarning + Error + Critical
Debug Logs May Be Absent Backend executors must explicitly call ctx.Logger.LogDebug(...) to emit debug-level logs. Many built-in nodes only log at Info and above. If no Debug entries appear, the executor does not emit them.