otel-logs

Validate OpenTelemetry logs and traces arriving in Seq via API.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ngareleo/xstream --skill otel-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otel-logs
Source: https://github.com/ngareleo/xstream/tree/main/.claude/skills/otel-logs
Command: npx skills add https://github.com/ngareleo/xstream --skill otel-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that the application's logging and tracing data are correctly arriving in the Seq system for accurate monitoring and diagnostics.

Core Features & Use Cases

  • Log and Trace Verification: Checks the availability and correctness of logs and traces from the server.
  • Monitoring Infrastructure Health: Validates the instrumentation pipeline's integrity after deployment or configuration changes.
  • Use Case: After deploying a new version of the server, use this Skill to confirm that traces and logs are correctly visible and connected.

Quick Start

Use the otel-logs skill to verify that traces and logs are arriving in Seq by specifying the trace id of recent playback.

Frequently Asked Questions about otel-logs

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

FAQPage Schema
How do I verify OpenTelemetry logs and traces are arriving in Seq?

To verify OpenTelemetry logs and traces in Seq, query the Seq API using curl and jq to check for specific span presence and trace integrity, confirming your server's observability pipeline is healthy.

How can I check if my server logs and traces are linked after a deployment?

Check server log and trace linkage after deployment by querying the Seq API for a specific trace id, validating that the OpenTelemetry instrumentation correctly connects logs and traces for debugging.

Do I need curl and jq to validate OpenTelemetry trace integrity in Seq?

Yes, you need curl and jq to validate OpenTelemetry trace integrity in Seq, as these tools are required to query and analyze the trace data directly from the Seq API.

What is the best way to monitor observability infrastructure health for OTLP data?

The best way to monitor observability infrastructure health for OTLP data is to validate the instrumentation pipeline's integrity by confirming that server logs and traces are correctly arriving and linked in Seq.

Why are my OpenTelemetry logs not showing up in Seq after configuration changes?

OpenTelemetry logs may not show up in Seq due to broken instrumentation pipelines; use this verification process to check trace availability and correctness by querying the Seq API for recent playback trace ids.