Comments are the lightest weight way to annotate traffic during a debugging session, and being able to revisit only the exchanges you flagged is a real productivity boost. The hasCommentFilter makes that selection trivial, whether you are driving a view filter in the desktop client or running a post capture workflow against a saved trace.
Reach for hasCommentFilter to single out exchanges that already have a comment attached. The filter is out of scope for the live HTTP flow, which means it is meant for view filtering, internal actions, and post capture workflows rather than mid request mutation.
Useful for:
Apply a tag to all commented exchanges so you can group them in the session viewer or rerun a later workflow.
rules:
- filter:
typeKind: HasCommentFilter
actions:
- typeKind: ApplyTagAction
tag:
value: reviewed
Combine with hasTagFilter (inverted) to identify exchanges that were commented but not yet tagged for follow up.
rules:
- filter:
typeKind: FilterCollection
operation: And
children:
- typeKind: HasCommentFilter
- typeKind: HasTagFilter
inverted: true
actions:
- typeKind: ApplyTagAction
tag:
value: needs-tag
Flip the filter to surface exchanges with no comment yet, useful when you want to make sure every interesting call was annotated.
rules:
- filter:
typeKind: HasCommentFilter
inverted: true
actions:
- typeKind: ApplyTagAction
tag:
value: needs-review
Select exchanges having comment.
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.
hasCommentFilter
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 |
The following examples apply a comment to the filtered exchange
Select exchanges having comment.
rules:
- filter:
typeKind: HasCommentFilter
actions:
- typeKind: ApplyCommentAction
comment: filter was applied
View definition of HasCommentFilter for .NET integration.
The following filters are related to this filter:
Comments are an annotation layer that lives on the captured exchange, not on the wire. The filter therefore makes sense for view filters and post capture operations rather than real time rules.
No. The filter only checks whether a comment exists. Use commentSearchFilter if you need to match comment text.
Yes. Pair it with a view filter or rerun the rule file against a saved session to extract annotated exchanges in bulk.