loki

Query Loki endpoints to analyze Kubernetes logs and troubleshoot cluster issues.

24|3|Updated Mar 31, 2022
One-click install
npx skills add https://github.com/ionfury/homelab --skill loki-ionfury
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loki
Source: https://github.com/ionfury/homelab/tree/main/.claude/skills/loki
Command: npx skills add https://github.com/ionfury/homelab --skill loki-ionfury

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Loki-based log querying for Kubernetes clusters to diagnose issues by searching logs, events, and patterns across environments.

Core Features & Use Cases

  • Loki-based log queries: perform instant, range, tail, label, and series queries against Loki at a configurable URL.
  • Kubernetes log debugging: inspect logs for pods, namespaces, and services to troubleshoot deployments or Flux reconciliations.
  • Cluster-wide triage: quickly identify issues across dev, integration, and live clusters with health checks and log streams.

Quick Start

Tail recent logs from a target namespace to quickly identify issues.

Frequently Asked Questions about loki

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

FAQPage Schema
How do I query Loki logs to troubleshoot Kubernetes cluster issues?

To query Loki logs for Kubernetes troubleshooting, use a Bash script to execute LogQL queries against Loki endpoints, enabling searches across pods, namespaces, and services to pinpoint deployment failures.

What types of LogQL queries can I run against Loki for cluster debugging?

You can run instant, range, tail, label, and series LogQL queries against Loki to inspect Kubernetes logs and events, with configurable time ranges and output formatting for effective cluster triage.

Can I search Kubernetes pod logs and events across multiple environments using Loki?

Yes, you can search Kubernetes pod logs and events across dev, integration, and live environments by querying Loki to identify platform service failures or Flux reconciliation issues.

Do I need curl and jq installed to query Loki logs for Kubernetes debugging?

Yes, you need curl, jq, and python3 installed as dependencies to execute the Bash script that queries Loki endpoints and formats log outputs for Kubernetes cluster debugging.

What is the best way to triage platform service failures across dev and live clusters?

The best way to triage platform service failures across dev and live clusters is querying Loki with range and tail queries to stream recent logs from target namespaces and run health checks.

Why is my Loki log query not returning results for a specific Kubernetes namespace?

A Loki log query may not return results for a Kubernetes namespace if the time range is incorrect or labels do not match, requiring label and series queries to verify available log streams.