feat(inbound-api): Log global for method scripts, central ScriptLog rows when traced (D4/D5)
This commit is contained in:
@@ -69,4 +69,17 @@ public class InboundApiOptions
|
||||
/// is still legitimately working and moves on to the next one. Default 60 s.
|
||||
/// </summary>
|
||||
public TimeSpan StandbyForwardTimeout { get; set; } = TimeSpan.FromSeconds(60);
|
||||
|
||||
/// <summary>Default value of <see cref="MaxLogLinesPerRun"/>, also used when no options instance is available.</summary>
|
||||
public const int DefaultMaxLogLinesPerRun = 200;
|
||||
|
||||
/// <summary>
|
||||
/// Flow Debugger step logs (design 2026-09-09 D7): how many <c>Log.*</c> lines ONE traced
|
||||
/// method execution may turn into <c>ScriptTrace/ScriptLog</c> audit rows. Past the cap the
|
||||
/// lines are dropped from the trace — they still reach the node's <c>ILogger</c> — and the
|
||||
/// run ends with a single runtime-sourced warning row naming the dropped count, so a
|
||||
/// truncated trace is never silently short. Untraced executions emit no rows at all and are
|
||||
/// therefore unaffected by this value. Must be greater than zero.
|
||||
/// </summary>
|
||||
public int MaxLogLinesPerRun { get; set; } = DefaultMaxLogLinesPerRun;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user