Read API Logs

Parse and filter UniManage API logs by date, endpoint, username, status code, and trace ID.

Updated Feb 27, 2025
One-click install
npx skills add https://github.com/tchiphuong/UniManage --skill read-api-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Read API Logs
Source: https://github.com/tchiphuong/UniManage/tree/main/backend/.agent/skills/read-api-logs
Command: npx skills add https://github.com/tchiphuong/UniManage --skill read-api-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps troubleshoot and diagnose issues with the UniManage API by providing a structured way to access, read, and analyze application logs.

Core Features & Use Cases

  • Log Analysis: Investigate API errors, performance bottlenecks, and unexpected behavior by examining log files.
  • Troubleshooting: Pinpoint the root cause of issues by filtering logs based on timestamps, usernames, status codes, and trace IDs.
  • Use Case: If a user reports that creating a new department failed, you can use this Skill to find the relevant error logs, identify the specific exception, and determine if it was a database constraint violation or a validation error.

Quick Start

Analyze the API logs from today for any errors related to the 'Users' endpoint.

Frequently Asked Questions about Read API Logs

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

FAQPage Schema
How do I analyze UniManage API logs to troubleshoot endpoint errors?

You can analyze UniManage API logs by parsing JSON-formatted entries stored in the backend/logs directory. This Skill enables troubleshooting by filtering log data based on date, API endpoint, username, status code, and trace ID using PowerShell commands.

What is the best way to investigate API performance bottlenecks using trace IDs?

Investigating API performance bottlenecks with trace IDs involves filtering JSON log entries to track individual request lifecycles. This Skill supports parsing UniManage application logs by trace ID to pinpoint slow responses and unexpected behavior.

Can I filter JSON application logs by username and status code in PowerShell?

Yes, you can filter JSON application logs by username and status code using PowerShell commands. This Skill facilitates querying the UniManage API logs to isolate specific user activities and HTTP response errors for detailed investigation.

How do I find the root cause of a failed API operation in backend log files?

To find the root cause of a failed API operation, you parse the backend log files to identify specific exceptions. This Skill helps diagnose whether issues like a failed department creation stem from database constraint violations or validation errors.

Does this log analysis approach require access to the backend/logs directory?

Yes, this log analysis approach requires access to the UniManage backend/logs directory where JSON-formatted log entries are stored. It operates directly on these application logs to facilitate error investigation and user activity tracking.