skills.rest
redhat-et
redhat-etOFFICIAL
Explore all skills by this author →
WebsiteGitHub

check-logs

Query and analyze Kagenti platform logs with Grafana Loki to detect errors.

1|1|Updated Nov 5, 2025
Search Tags:#debugging#error detection#troubleshooting#logs#observability#Loki#Grafana
One-click install
npx skills add https://github.com/redhat-et/kagenti-demo-deployment --skill check-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-logs
Source: https://github.com/redhat-et/kagenti-demo-deployment/tree/main/.claude/skills/check-logs
Command: npx skills add https://github.com/redhat-et/kagenti-demo-deployment --skill check-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sifting through distributed logs across many pods and namespaces to find specific errors is time-consuming and complex. This skill streamlines log querying and analysis using Grafana Loki, enabling quick error detection and efficient debugging, reducing downtime and investigation effort.

Core Features & Use Cases

  • Centralized Log Search: Query logs by namespace, pod, container, or log level across the entire platform.
  • Error & Warning Detection: Quickly identify critical issues and potential problems in log streams.
  • Debugging Assistance: Analyze log patterns to diagnose pod crashes, restarts, and application behavior.
  • Use Case: The kagenti-operator pod is restarting frequently. Use this skill to retrieve the logs from the previous container of the kagenti-operator to understand why it crashed.

Quick Start

Use the check-logs skill to show me the error logs from the keycloak namespace in the last 10 minutes.

Frequently Asked Questions about check-logs

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

FAQPage Schema
How do I query logs from Grafana Loki to find errors across pods and namespaces?▼

Query logs from Grafana Loki by specifying namespace, pod, container, and log level filters using LogQL syntax. The check-logs skill retrieves centralized logs across your platform, enabling you to pinpoint errors and warnings in seconds rather than manually searching individual pod logs.

Can I search logs by time range and log level to debug pod crashes?▼

Yes. Time-based queries and log level filtering let you isolate critical errors within a specific window. Use this to analyze crash patterns—for example, retrieving previous container logs from a restarting pod to diagnose why it failed.

What's the best way to aggregate logs across multiple pods in the same namespace?▼

Cross-pod log aggregation in Loki consolidates logs from all pods in a namespace into a single queryable stream. This eliminates switching between individual pod logs and reveals patterns across your deployment, accelerating root-cause analysis.

How do I detect error patterns in application logs using log queries?▼

Log-pattern detection with LogQL queries identifies recurring error signatures and anomalies across your logs. The skill provides example queries and CLI usage to match specific error strings, stack traces, or warning thresholds in your application output.

Do I need prior experience with LogQL to use this skill for debugging?▼

No. The skill includes example LogQL queries and CLI commands ready to use. Beginners can start with provided templates to query by namespace and pod; advanced users can write custom LogQL patterns for deeper log analysis.

Related Skills

Explore More Software Engineering Skills→
julianobarbosajulianobarbosa
7

loki

Deploy Grafana Loki with Helm and configure LogQL queries.

Community
Advanced
ntaksh42ntaksh42
1

log-analyzer

Analyze application logs to detect errors, patterns, and anomalies.

Community
Intermediate
timequitytimequity
6

monitoring-setup

Set up Prometheus, Grafana, Loki, and Jaeger for Kubernetes observability.

Official
Advanced
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

log-aggregation-configurator

Configure centralized logging with ELK, Loki, or Splunk across services and environments.

Official
Intermediate