statusCodeServerErrorFilter Filter

Select exchanges whose response status code falls in the 5XX server or intermediary error range, the natural scope for outage triage and alerting.

statusCodeServerErrorFilter is the concise way to surface every 5XX response in a Fluxzy session. Pair it with capture, logging or tagging actions to build a live triage workflow without enumerating each individual code.

When to use this filter

Use statusCodeServerErrorFilter when you want a rule that fires for any 5XX response, which captures the full family of server or intermediary errors. This is the right filter for outage triage and live incident workflows where the exact code matters less than the fact that something failed on the server side.

Typical situations:

Capturing every 5XX response during a live incident for offline post mortem analysis.
Tagging server errors with a consistent label so they can be pivoted in the timeline.
Logging a structured line to stderr or a file whenever a 5XX is observed.

The filter evaluates on the responseHeaderReceivedFromRemote scope, so the status code is already known when it runs. Use statusCodeFilter if you need to react only to a specific code such as 502 or 504.

Real world examples

Capture every 5XX response to a dedicated session

Send all server errors to a separate capture so you can review the surrounding traffic later without sifting through successful exchanges.

rules:
- filter:
    typeKind: StatusCodeServerErrorFilter
  actions:
  - typeKind: CaptureSessionAction

Log a structured line for every server error

Write a one line summary to stderr whenever a 5XX is observed, useful when running Fluxzy under a process supervisor that collects logs centrally.

rules:
- filter:
    typeKind: StatusCodeServerErrorFilter
  actions:
  - typeKind: StdErrAction
    line: 'server-error observed'

Tag every server error for triage

Apply a tag to any 5XX exchange so an incident channel can filter the timeline to only the failing requests.

rules:
- filter:
    typeKind: StatusCodeServerErrorFilter
  actions:
  - typeKind: ApplyTagAction
    tag:
      value: server-error

Reference

statusCodeServerErrorFilter

Description

Select exchanges that HTTP status code indicates a server/intermediary error (5XX).

Evaluation scope

Evaluation scope defines the timing where this filter will be applied.

responseHeaderReceivedFromRemote This scope occurs the moment fluxzy has done parsing the response header.

YAML configuration name

statusCodeServerErrorFilter

Settings

This filter has no specific characteristic

The following table describes the customizable properties available for this filter:

Property	Type	Description	DefaultValue
inverted	boolean	Negate the filter result	false

Example of usage

The following examples apply a comment to the filtered exchange

Select exchanges that HTTP status code indicates a server/intermediary error (5XX).

rules:
- filter:
    typeKind: StatusCodeServerErrorFilter
  actions:
  - typeKind: ApplyCommentAction
    comment: filter was applied

.NET reference

View definition of StatusCodeServerErrorFilter for .NET integration.

Frequently asked questions

Which codes does it cover?

Every status code in the 500 to 599 range, including the well known 500, 502, 503 and 504 plus any non standard 5XX returned by intermediaries.

Does it also include 5XX responses produced by Fluxzy itself?

Yes, as long as the response is what the client actually receives. Synthesized 5XX responses generated by a previous action are still matched.

How is it different from statusCodeFilter?

statusCodeFilter requires an explicit list of codes. statusCodeServerErrorFilter is a class shortcut that always covers the whole 5XX range.

Can I exclude 5XX traffic from another rule?

Yes, set inverted: true. The rule then fires for every response that is not in the 5XX range.

Learn more about Fluxzy rules

Rule file syntax reference Importing YAML rules into Fluxzy Desktop Using rule files with Fluxzy CLI

Browse all directives