graylog
/graylog
Use when the user wants to search, query, or investigate production logs via Graylog. Covers concepts (streams, trace_id, log levels, query syntax) and routes to specialty skills for deeper debugging flows. Triggers on "graylog", "check logs", "search logs", "find the log for", "what does graylog say", "grep logs".
- Author
- pranavj17 ↗
- Repository
- mcp-server-graylog ↗
- Licence
- MIT
- Last repository change
- 25.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants to search, query, or investigate production logs via Graylog. Covers concepts (streams, trace_id, log levels, query syntax) and routes to specialty skills for deeper debugging flows. Triggers on "graylog", "check logs", "search logs", "find the log for", "what does graylog say", "grep logs".
Triggers from the description
Original author description
Use when the user wants to search, query, or investigate production logs via Graylog. Covers concepts (streams, trace_id, log levels, query syntax) and routes to specialty skills for deeper debugging flows. Triggers on "graylog", "check logs", "search logs", "find the log for", "what does graylog say", "grep logs".
How it works
- Quick map: question → tool
- Core concepts
- Query syntax
- Result limits
- When to hand off
- Defaults that matter
SKILL.md preview
--- name: graylog description: Use when the user wants to search, query, or investigate production logs via Graylog. Covers concepts (streams, trace_id, log levels, query syntax) and routes to specialty skills for deeper debugging flows. Triggers on "graylog", "check logs", "search logs", "find the log for", "what does graylog say", "grep logs". --- # Graylog MCP — Entry Point You have access to a Graylog MCP server with 8 tools for log search, distributed tracing, and incident investigation. This skill teaches you which tool to reach for and when to hand off to a specialty skill. ## Quick map: question → tool | If the user says... | Reach for | And then... | |---|---|---| | "I have a trace_id, what happened" | `trace_request` | If >200 lines or >5 services, dispatch the `graylog-trace-analyzer` agent. Otherwise see `trace-debugging` skill. | | "Errors are spiking" / "something just broke" | `aggregate_logs` (group_by: service, query: `logger_level:error`) | See `incident-triage` skill. | | "What was happening around time T on host H" | `get_surrounding_logs` | Center timestamp + source filter. | | "Show me logs matching X in the last N minutes" | `search_logs_relative` | Default fields are fine for most cases. | | "Show me logs between timestamps A and B" | `search_logs_absolute` | Use UTC ISO 8601. | | "What streams / applications exist" | `list_streams` | Use IDs returned to filter subsequent searches. | | "Is Graylog reachable" | `get_system_info` | Always run this first if other tools fail (see `troubleshooting` skill). | ## Core concepts - **Stream** — a Graylog stream is roughly one application or log source. Use `list_streams` to discover IDs, then pass `streamId` to filter. - **trace_id / span_id** — distributed trace correlation IDs. A single request will have one trace_id across all services that handle it. `span_id` identifies a unit of work within the trace. - **Levels** — common: `error`, `warn`, `info`, `debug`. Filter via `logger_level:error`. - **Time windows** — choose absolute (`from`/`to` ISO 8601 UTC) for known incidents; relative (`rangeSeconds`) for "the last N minutes." ## Query syntax Graylog uses Elasticsearch query string syntax: - Field filter: `logger_level:error`, `service:foo` - Boolean: `logger_level:error AND service:foo` - Phrase: `"GET /api/v1/users"` (quoted) - Wildcard: `service:foo-*` - Negation: `NOT service:health-check` ## Result limits - Default 50, max 1000 results per call. - If a search hits the cap, narrow the time window before raising the limit. - For `aggregate_logs`, if `truncated: true` appears in the response, the matched window exceeded `fetchLimit` (default 5000) — narrow the time range. ## When to hand off - Trace investigations → `trace-debugging` skill (single-service inline) or `graylog-trace-analyzer` agent (multi-service, log-heavy) - Active incidents → `incident-triage` skill - Tools returning errors / empty results → `troubleshooting` skill ## Defaults that matter - Searches return `message,timestamp,source,level,logger_level,trace_id,span_id,pod,service,container_name` by default. That covers most debugging without needing `*`. - Pass `fields: '*'` only when you need a field outside the default set — it increases response size significantly.
Versions
The database has no other skills named graylog.
Database snapshot: 13.11.2026 · package version 23eff4442d8b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100graylog-search
Search any Graylog instance from the CLI via its REST API. Use when debugging a production incident, verifying a deploy, or hunting an error in service logs aggregated in Graylog. Covers API-token auth, the universal search endpoints (relative/absolute/histogram/terms), Lucene… - 100troubleshooting
Use when Graylog MCP tools return errors (connection refused, 401, target not found, empty results when results are expected). Diagnoses connectivity, auth, and configuration. Triggers on graylog tool failures, "connection refused", "401", "target not found", "graylog isn't returning anything". - 100victorialogs-query
Query VictoriaLogs via curl. Use when searching logs with LogsQL, running log stats queries, discovering log fields/streams, analyzing log hit patterns, or exploring log facets. Triggers on: log queries, LogsQL, log search, log stats, field discovery, stream discovery, log… - 100structured-logging-design
Use when designing log schemas, choosing JSON vs text logs, setting up correlation IDs across services, redacting PII, controlling log volume costs, or wiring logs into OpenTelemetry. Triggers: "logs are unsearchable", trace_id missing from logs, PII leak in production logs, log… - 100server-application-log-analysis-grep-sed
Use this skill when extract critical error patterns, trace IDs, and anomalies from raw server logs using CLI tools. - 100datadog
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.