Streaming a one line summary per matching exchange turns Fluxzy into a tiny observability tool. Pipe the output into grep, awk, or your favorite line based aggregator, and you have a live filter view of the only requests that matter to you.
Use stdOutAction to emit a line of text on standard output every time a filter matches. The action supports {{variable}} substitution, which lets you build readable summaries that include the URL, status code, host, or any variable you previously set with setVariableAction.
Typical uses:
Pair the action with a tight filter, because stdout can fill quickly. If you only care about a subset of the lifecycle, use runScope to restrict execution to one stage of the exchange.
Lightweight tail style logging you can pipe into grep or jq friendly tooling.
rules:
- filter:
typeKind: HostFilter
pattern: api.example.com
actions:
- typeKind: StdOutAction
text: "{{method}} {{authority}}{{url}}"
Use a runScope so the line is emitted after the response header is parsed, when the status code is known.
rules:
- filter:
typeKind: PathFilter
pattern: /checkout
actions:
- typeKind: StdOutAction
text: "checkout response: {{statusCode}}"
runScope: responseHeaderReceivedFromRemote
Capture a tenant id once with setVariableAction and reuse it in every log line for that exchange.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: SetVariableAction
name: tenant
value: acme
- typeKind: StdOutAction
text: "tenant={{tenant}} url={{url}}"
Write text to standard output. Captured variable are interpreted.
Evaluation scope defines the timing where this filter will be applied.
outOfScope Means that the filter or action associated to this scope won't be trigger in the regular HTTP flow. This scope is applied only on view filter and internal actions.
stdOutAction
The following table describes the customizable properties available for this action:
| Property | Type | Description | DefaultValue |
|---|---|---|---|
| text | string | ||
| runScope | nullable`1 | When RunScope is defined. The action is only evaluated when the value of the scope occured. |
This filter has no specific usage example
View definition of StdOutAction for .NET integration.
The following actions are related to this action:
Exchange properties such as url, authority, method, statusCode, and any variable you previously defined with setVariableAction or applyTagAction. Variables not yet available on the current scope render as empty strings.
stdOutAction writes to the process stdout stream and is best for ad hoc inspection or piping. fileAppendAction persists the same text to a file on disk for long term capture.
Yes. Set the runScope property to a specific stage such as responseBodyReceivedFromRemote. Without runScope, the action runs at the scope inherited from its filter.
Standard out is fast on Linux and macOS, but uncontrolled logging in a high traffic environment can fill the terminal or fill a container log volume. Use tight filters and limit the action to interesting subsets.