relatedlogs

Retrieve related Loki logs for a selected metric in Grafana Metrics Drilldown.

31|18|Updated Oct 15, 2024
One-click install
npx skills add https://github.com/grafana/metrics-drilldown --skill relatedlogs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relatedlogs
Source: https://github.com/grafana/metrics-drilldown/tree/main/.claude/skills/generated/relatedlogs
Command: npx skills add https://github.com/grafana/metrics-drilldown --skill relatedlogs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section describes how the RelatedLogs area helps correlate Prometheus metrics with Loki logs to speed up root-cause analysis and observability.

Core Features & Use Cases

  • Navigate between metrics and Loki logs to identify anomalies and correlated events.
  • Understand how RelatedLogs orchestrator methods like addLokiDataSourcesChangeHandler, handleFiltersChange, and findAndCheckAllDatasources interact to refresh results.
  • Use Case: When a spike occurs in a metric, quickly surface matching logs across data sources to pinpoint the underlying event.

Quick Start

Run the RelatedLogs workflow to surface matching logs for a selected metric in Metrics Drilldown.

Frequently Asked Questions about relatedlogs

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

FAQPage Schema
How do I find related logs for a Prometheus metric spike in Grafana?

To find related logs for a Prometheus metric spike, use the RelatedLogs workflow within Grafana Metrics Drilldown. It automatically correlates your selected metrics with Loki log streams across multiple data sources to pinpoint underlying events.

How does Grafana correlate metrics with Loki log streams during root-cause analysis?

Grafana correlates metrics with Loki log streams by orchestrating cross-source data retrieval. The RelatedLogs area applies filter handling and data-source orchestration to automatically surface matching log events for observed metric anomalies.

Can I explore logs across multiple Loki data sources when debugging performance issues?

Yes, you can explore logs across multiple Loki data sources when debugging performance issues. The system uses orchestrator methods to find and check all available datasources, refreshing log counts and results based on applied filters.

What is the best way to drill down from metrics to logs for observability insights?

The best way to drill down from metrics to logs is using the RelatedLogs workflow in Grafana Metrics Drilldown. It enables seamless navigation between Prometheus metrics and Loki logs to identify correlated anomalies and speed up root-cause analysis.

Do I need to manually configure filters when navigating between metrics and Loki logs?

No, manual filter configuration is not needed when navigating between metrics and Loki logs. The system automatically handles filter changes through dedicated orchestrator methods, continuously refreshing log results to match your active metric context.