triage-logs

Analyze device log bundles with Telemetry 2.0 source code to identify issues.

1|23|Updated Jan 24, 2025
One-click install
npx skills add https://github.com/rdkcentral/telemetry --skill triage-logs-rdkcentral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-logs
Source: https://github.com/rdkcentral/telemetry/tree/main/.github/skills/triage-logs
Command: npx skills add https://github.com/rdkcentral/telemetry --skill triage-logs-rdkcentral

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to triaging Telemetry 2.0 behavioral issues by correlating device log bundles with source code, helping to identify root causes and propose test scenarios.

Core Features & Use Cases

  • Log Bundle Analysis: Correlate device log bundles with source code for systematic root-cause analysis.
  • Issue Characterization: Covers various issues such as hangs, under-reporting, over-reporting, and CPU/memory spikes.
  • Test Scenario Generation: Proposes unit-test and functional-test reproduction scenarios.
  • Use Case: When faced with a Telemetry 2.0 anomaly, this Skill guides you through the process of understanding the logs, mapping profiles and threads, identifying the anomaly window, and locating the code path.

Quick Start

To start the triage process, use the triage-logs skill with a device log bundle and describe the issue you're facing.

Frequently Asked Questions about triage-logs

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

FAQPage Schema
How do I analyze RDK device log bundles to find the root cause of a Telemetry 2.0 issue?

To perform root cause analysis, you analyze RDK device log bundles alongside Telemetry 2.0 source code to systematically map profiles, identify the anomaly window, and locate the failing code path.

What is the best way to triage RDK telemetry anomalies like under-reporting or CPU spikes?

Triage RDK telemetry anomalies by correlating device log bundles with Telemetry 2.0 source code. This process characterizes behavioral issues such as under-reporting, over-reporting, hangs, and CPU spikes.

Do I need Telemetry 2.0 source code access to diagnose RDK device log issues?

Yes, diagnosing RDK device log issues requires knowledge of Telemetry 2.0 architecture and source code access to correlate the logs with the system's actual code paths for effective issue characterization.

How can I generate test scenarios from RDK telemetry log analysis?

Generate test scenarios from RDK telemetry log analysis by using the triage results to propose unit-test and functional-test reproduction scenarios that replicate the identified device telemetry anomaly.

Can I use this approach to identify why my RDK device telemetry is hanging?

Yes, you can identify why RDK device telemetry is hanging by analyzing the device log bundles within the anomaly window and mapping the telemetry profiles and threads to the corresponding source code.

What are the limitations of correlating RDK device logs with telemetry source code?

The limitation of correlating RDK device logs with telemetry source code is that accurate root cause analysis strictly depends on having comprehensive log bundles and deep knowledge of the Telemetry 2.0 architecture.