job-logs

Extracts job execution logs with I/O streams and timestamps from Weaver API-driven systems.

30|6|Updated Mar 5, 2019
One-click install
npx skills add https://github.com/crim-ca/weaver --skill job-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-logs
Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/job-logs
Command: npx skills add https://github.com/crim-ca/weaver --skill job-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The job-logs skill helps users retrieve and analyze execution logs to debug and monitor job executions.

Core Features & Use Cases

  • Retrieve Logs: Access detailed information such as process execution steps, standard output/error, and timestamps.
  • Debugging: Debug failed jobs and identify the root cause of failures.
  • Monitoring: Track job execution details for ongoing performance analysis.

Quick Start

To get the job logs for a specific job, use the following command: weaver logs -u $WEAVER_URL -j a1b2c3d4-e5f6-7890-abcd-ef1234567890.

Frequently Asked Questions about job-logs

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

FAQPage Schema
How do I retrieve execution logs for debugging a failed job?

To retrieve execution logs for debugging a failed job, use the command `weaver logs -u $WEAVER_URL -j [job_id]` to extract process execution steps, standard I/O streams, and timestamps.

What details can I extract from job execution logs for monitoring?

Job execution logs provide process execution steps, standard output and error streams, and precise timestamps to track job performance and monitor ongoing execution details within a Weaver API-driven system.

Can I use this to monitor job performance within a Weaver API-driven system?

Yes, you can monitor job performance within a Weaver API-driven system by accessing execution logs to track process execution details and standard I/O streams for ongoing performance analysis.

How do I identify the root cause of failed jobs using standard I/O streams?

You identify the root cause of failed jobs by accessing execution logs to analyze standard output and error streams, which provide detailed process execution steps and timestamps for debugging.

Does the job-logs skill require any specific dependencies to access execution logs?

No specific dependencies are required to access execution logs, making it straightforward for system administrators and developers to retrieve process execution details and standard I/O streams.

What is the best way to track job execution details for ongoing performance analysis?

The best way to track job execution details for ongoing performance analysis is accessing execution logs via the Weaver API, which extracts process steps, standard I/O streams, and timestamps.