seq

Retrieve and filter logs and trace spans from a local Seq server via its HTTP API.

1|Updated Apr 10, 2026

Search Tags:#debugging #monitoring #logs #api #logging #traces #seq

Ready to run

npx skills add https://github.com/ngareleo/xstream --skill seq-ngareleo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: seq
Source: https://github.com/ngareleo/xstream/tree/main/.claude/skills/seq
Command: npx skills add https://github.com/ngareleo/xstream --skill seq-ngareleo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables efficient retrieval and analysis of logs and traces from a local Seq server through its HTTP API, eliminating the need for manual browser-based inspection.

Core Features & Use Cases

Log and Trace Retrieval: Fetch logs and trace spans directly via API calls using filters for specific trace IDs, span names, or severity levels.
Data Parsing and Filtering: Extract relevant event properties and format them for further analysis or scripting.
Use Case: Analyzing a trace to diagnose a performance issue by filtering spans with a specific trace ID and inspecting their properties for anomalies.

Quick Start

Use the seq skill to fetch recent error logs and inspect spans related to a specific trace ID.

Frequently Asked Questions about seq

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

FAQPage Schema

How do I retrieve logs and trace spans from a local Seq server via API?▼

Retrieve logs and trace spans from a local Seq server by querying its HTTP API. The process involves authenticating via session cookies and using curl with jq to fetch and parse distributed trace data for monitoring or debugging.

What's the best way to filter Seq logs by trace ID or severity level?▼

Filter Seq logs by trace ID, span name, or severity level through direct API calls. This method extracts relevant event properties and formats them, allowing detailed investigation of distributed traces and specific span activities.

Do I need curl and jq to analyze distributed traces from Seq?▼

Yes, you need curl and jq to analyze distributed traces from Seq. These dependencies are required for making HTTP API requests to the Seq server and parsing the returned JSON log data for further filtering and analysis.

Can I diagnose performance issues by inspecting trace span properties in Seq?▼

Yes, you can diagnose performance issues by inspecting trace span properties in Seq. By filtering spans for a specific trace ID and examining their extracted properties, you can identify anomalies within your distributed system's log levels.

How does session cookie authentication work for local Seq log retrieval?▼

Session cookie authentication secures access when retrieving logs from a local Seq server. It validates your HTTP API requests, ensuring that only authorized users can fetch and filter sensitive trace spans and log data during investigations.

Are there limitations to analyzing Seq logs locally instead of through a browser?▼

Analyzing Seq logs locally via API eliminates manual browser inspection but requires specific command-line tools. You must handle data parsing and filtering yourself, though this enables better scripting and detailed automated investigations.