hasTagFilter Filter

Q: Can I combine multiple tag checks?

Yes. Wrap several `hasTagFilter` (or other filters) inside a `FilterCollection` to compose with `And` and `Or` operations.

Match exchanges that already carry a tag, so you can drive view filters, exports, and follow up actions on previously labelled traffic.

Tags are the most lightweight way to categorize traffic in Fluxzy, and being able to revisit only the exchanges you have labelled is invaluable during a long debugging session. The hasTagFilter makes that selection trivial, whether you are driving a desktop view filter or running a post capture rule pass against a saved trace.

When to use this filter

Use hasTagFilter to single out exchanges that already carry a tag, regardless of the tag value. The filter is out of scope for the live HTTP flow, so it is intended for view filters, exports, and post capture workflows rather than mid request mutation.

Helpful for:

Driving a view filter in the desktop client that shows only labelled traffic.
Running a follow up rule pass on previously categorized exchanges.
Detecting exchanges that should have been tagged but were missed (using inverted: true).

Real world examples

Annotate tagged exchanges with a review comment

Mark every tagged exchange with a comment so reviewers know it was already triaged.

rules:
- filter:
    typeKind: HasTagFilter
  actions:
  - typeKind: ApplyCommentAction
    comment: previously triaged

Find exchanges that have a tag but no comment

Spot tagged exchanges that still need a human note attached.

rules:
- filter:
    typeKind: FilterCollection
    operation: And
    children:
    - typeKind: HasTagFilter
    - typeKind: HasCommentFilter
      inverted: true
  actions:
  - typeKind: ApplyTagAction
    tag:
      value: needs-comment

Invert it to find unlabelled traffic

Surface exchanges that escaped tagging during a triage pass, so you can review them.

rules:
- filter:
    typeKind: HasTagFilter
    inverted: true
  actions:
  - typeKind: ApplyTagAction
    tag:
      value: untagged

Reference

hasTagFilter

Description

Select exchanges having tag.

Evaluation scope

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.

YAML configuration name

hasTagFilter

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 having tag.

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

.NET reference

View definition of HasTagFilter for .NET integration.

Frequently asked questions

Why is this filter out of scope for live traffic?

Tags are an annotation that lives on captured exchanges, not on the wire. The filter is therefore meant for view filtering and post capture workflows, not for mid request mutation.

Does the tag value matter?

No. The filter triggers on the presence of any tag. Use a dedicated value check or a commentSearchFilter for finer matching.

Can I combine multiple tag checks?

Yes. Wrap several hasTagFilter (or other filters) inside a FilterCollection to compose with And and Or operations.

Learn more about Fluxzy rules

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

Browse all directives