Range filter plugin

Checks numeric values or string lengths against bounds and applies actions when an event is inside or outside the expected range.

• Package: logstash-filter-range
• Coverage source: default/bundled, explicitly installed in the Logit image
• Official catalog entry: Yes

Plugin overview

range is used in the Logstash filter stage. Checks field values against numeric or length bounds.

Typical use cases

• Transform fields before indexing to keep schema and naming consistent.
• Prepare high-quality fields for alerts, dashboards, and downstream pipelines.

Input and output behavior

• Flow: processes matching events and mutates fields/tags within the same event.
• Input: works on events that match your surrounding if conditions.
• Output: updates the current event in place unless configured otherwise.
• Important options: negate, ranges.

Options

Required

• No required plugin-specific options.

Optional

• negate (type: boolean; default: false) — Invert the match so actions fire when the value is outside the range.
• ranges (type: array; default: []) — Array of range rules; each rule is [ field, min, max, action ].

Example configuration

filter {
  range {
    ranges => [
      "[http][response][status_code]", 200, 299, "tag:status_2xx",
      "[http][response][status_code]", 500, 599, "tag:status_5xx",
      "message", 0, 2048, "tag:message_length_ok"
    ]
    negate => false
  }
}

Common options configuration

All Logstash filter plugins support these shared options:

• add_field (type: hash; default: {}) — Adds fields when the filter succeeds. Supports dynamic field names and values.
• add_tag (type: array; default: []) — Adds one or more tags when the filter succeeds.
• enable_metric (type: boolean; default: true) — Enables or disables metric collection for this plugin instance.
• id (type: string; default: none) — Sets an explicit plugin instance ID for monitoring and troubleshooting.
• periodic_flush (type: boolean; default: false) — Calls the filter flush method at regular intervals.
• remove_field (type: array; default: []) — Removes fields when the filter succeeds. Supports dynamic field names.
• remove_tag (type: array; default: []) — Removes tags when the filter succeeds.

filter {
  range {
    add_field => { "pipeline_stage" => "parsed" }
    add_tag => ["parsed", "logstash_filter"]
    enable_metric => true
    id => "my_filter_instance"
    periodic_flush => false
    remove_field => ["tmp_field"]
    remove_tag => ["temporary"]
  }
}

Apply in Logit.io

1. Open your stack in Logit.io and navigate to Logstash Pipelines.
2. In the filter { ... } section, add a range block.
3. Save your pipeline changes, then restart the Logstash pipeline if prompted.
4. Send sample events and verify parsed/enriched fields in OpenSearch Dashboards.

Validation checklist

• Confirm the range block compiles without syntax errors.
• Verify expected new/updated fields exist in sample documents.
• Verify unexpected fields are not removed unless explicitly configured.
• Confirm tags added on success/failure align with your alerting and routing rules.

Troubleshooting

• If events are unchanged, verify your filter condition (if ...) matches incoming events.
• If the pipeline fails to start, validate braces/quotes and retry with a minimal filter block.
• If throughput drops, reduce expensive operations and test with representative sample volume.

References

• GitHub package: logstash-filter-range (opens in a new tab)
• Canonical catalog: /log-management/ingestion-pipeline/logstash-filters-reference