---
id: ssh2-base44-troubleshooter
name: "base44-troubleshooter"
url: https://skills.yangsir.net/skill/ssh2-base44-troubleshooter
author: base44
domain: ai-system-observability-sre
tags: ["troubleshooting", "debugging", "system-diagnostics", "problem-solving", "technical-support"]
install_count: 9400
rating: 4.50 (53 reviews)
github: https://github.com/base44/skills
---

# base44-troubleshooter

> 利用后端函数日志，诊断并解决生产环境中的各类问题，确保系统稳定运行。

**Stats**: 9,400 installs · 4.5/5 (53 reviews)

## Before / After 对比

### 快速排查生产环境后端故障

## Readme

# Troubleshoot Production Issues

## Prerequisites

Verify authentication before fetching logs:

```bash
npx base44 whoami
```

If not authenticated or token expired, instruct user to run `npx base44 login`.

Must be run from the project directory (where `base44/.app.jsonc` exists):

```bash
cat base44/.app.jsonc
```

## Available Commands

| Command | Description | Reference |
|---------|-------------|-----------|
| `base44 logs` | Fetch function logs for this app | [project-logs.md](references/project-logs.md) |

## Troubleshooting Flow

### 1. Check Recent Errors

Start by pulling the latest errors across all functions:

```bash
npx base44 logs --level error
```

### 2. Drill Into a Specific Function

If you know which function is failing:

```bash
npx base44 logs --function <function_name> --level error
```

### 3. Inspect a Time Range

Correlate with user-reported issue timestamps:

```bash
npx base44 logs --function <function_name> --since <start_time> --until <end_time>
```

### 4. Analyze the Logs

- Look for stack traces and error messages in the output
- Check timestamps to correlate with user-reported issues
- Use `--limit` to fetch more entries if the default 50 isn't enough


---
*Source: https://skills.yangsir.net/skill/ssh2-base44-troubleshooter*
*Markdown mirror: https://skills.yangsir.net/api/skill/ssh2-base44-troubleshooter/markdown*