expanso-filter-severity

Filter log messages by severity and route them to different outputs.

1|Updated Feb 1, 2026

Search Tags:#logs #data pipeline #filtering #severity #expanso #log processing

Ready to run

npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-filter-severity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: expanso-filter-severity
Source: https://github.com/expanso-io/expanso-skills/tree/main/skills/recipes/filter-severity
Command: npx skills add https://github.com/expanso-io/expanso-skills --skill expanso-filter-severity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage log data by filtering out messages that do not meet a specified severity level, reducing noise and highlighting critical information.

Core Features & Use Cases

Dynamic Severity Filtering: Filters logs based on severity levels like ERROR, WARN, INFO, etc.
Flexible Input Handling: Processes both structured JSON logs and unstructured text logs.
Conditional Routing: Directs filtered logs to different outputs based on their severity.
Use Case: In a production environment, automatically route all ERROR level logs to a dedicated alert channel while sending WARN logs to a separate monitoring dashboard.

Quick Start

Run the filter-severity pipeline with sample data using the provided run script.

Frequently Asked Questions about expanso-filter-severity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I filter log messages by severity level in a data pipeline?▼

To filter log messages by severity level, you can use a pipeline that processes both JSON and structured text logs, routing ERROR logs to a file and WARN logs to stdout while normalizing severity levels.

Can I process unstructured text logs and route them based on severity?▼

Yes, you can process unstructured text logs by using intelligent severity detection to normalize levels, routing ERROR logs to a dedicated file and WARN logs to stdout for monitoring.

Do I need Expanso Edge to route logs by severity?▼

Yes, you need Expanso Edge and configured credentials to run the log processing pipeline for severity filtering and conditional routing of log messages.

What is the best way to separate ERROR and WARN logs for production monitoring?▼

The best way to separate ERROR and WARN logs is to use conditional routing, which directs ERROR logs to a dedicated alert file and WARN logs to stdout or a separate dashboard file.

How do I normalize log severity levels across mixed JSON and text formats?▼

You normalize log severity levels across mixed formats by using intelligent severity detection during log processing, ensuring consistent filtering before routing ERROR and WARN outputs.

What limitations exist when filtering structured text logs for severity?▼

When filtering structured text logs for severity, the main limitation is the dependency on Expanso Edge and configured credentials, as the pipeline requires this environment to process and route logs.