grafana-loki

Name: grafana-loki
Availability: InStock
Author: Lodekeeper

Query Grafana Loki logs for Lodestar beacon nodes, execution clients, and validators.

4|1|Updated Feb 20, 2026

Search Tags:#debugging #troubleshooting #logs #grafana #loki #lodestar

Ready to run

npx skills add https://github.com/lodekeeper/dotfiles --skill grafana-loki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grafana-loki
Source: https://github.com/lodekeeper/dotfiles/tree/main/skills/grafana-loki
Command: npx skills add https://github.com/lodekeeper/dotfiles --skill grafana-loki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows users to query logs from Grafana Loki, specifically for Lodestar beacon nodes, execution clients, and validators, enabling efficient debugging of system issues.

Core Features & Use Cases

Log Querying: Access and retrieve logs from various Lodestar components via Grafana's Loki datasource.
Debugging: Investigate node crashes, sync issues, communication errors, and performance problems.
Use Case: When a Lodestar beacon node unexpectedly restarts, use this Skill to query its logs for fatal errors or OOM messages that occurred just before the shutdown.

Quick Start

Use the grafana-loki skill to find all error messages in the beacon node logs for the 'unstable-super' instance over the last 6 hours.

Frequently Asked Questions about grafana-loki

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

FAQPage Schema

How do I query Lodestar beacon node logs in Grafana Loki after a crash?▼

To query Lodestar beacon node logs in Grafana Loki, use this Skill to execute LogQL syntax targeting the specific instance, filtering for fatal errors or OOM messages preceding the shutdown.

Can I debug execution client and validator synchronization issues using Grafana Loki?▼

Yes, you can debug execution client and validator synchronization issues using Grafana Loki by retrieving and analyzing logs from these Lodestar components to identify inter-client communication errors.

Do I need to know LogQL syntax to query logs from Lodestar infrastructure components?▼

Yes, understanding LogQL syntax is required to effectively query logs from Lodestar infrastructure components, alongside having active Grafana access to retrieve and analyze the log data.

What is the best way to find error messages in beacon node logs for a specific instance?▼

The best way to find error messages in beacon node logs is to query Grafana Loki using LogQL, targeting the specific instance name and filtering by time range to isolate performance anomalies.

Why does my Lodestar beacon node unexpectedly restart, and how can I check the logs?▼

To investigate why a Lodestar beacon node unexpectedly restarts, query its logs in Grafana Loki to find fatal errors or out-of-memory messages that occurred immediately before the shutdown event.