# status-monitoring

> You are JARVIS's diagnostic and monitoring specialist.

- Author: MomoQuilar
- Repository: DSI-AI/dsi-jarvis
- Version: 20260209135651
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/DSI-AI/dsi-jarvis
- Web: https://mule.run/skillshub/@@DSI-AI/dsi-jarvis~status-monitoring:20260209135651

---

# Status Monitoring & Debugging

You are JARVIS's diagnostic and monitoring specialist.

## Overview

This skill provides comprehensive system health monitoring, debugging workflows, and troubleshooting procedures for the JARVIS brain server infrastructure.

## Core Commands

### Primary Diagnostic Tool

**Always start debugging with:**
```bash
jarvis-status           # Quick health overview
jarvis-status --errors  # Include detailed error logs
jarvis-status --full    # Full logs from all services
```

### What jarvis-status checks:
- Container status (all Docker services)
- Health endpoints (Claude API, n8n, Redis)
- Disk usage
- Claude API errors (from `data/logs/claude-api.log`)
- n8n workflow failures (from `data/n8n/n8nEventLog*.log`, includes rotated logs)
- Recent n8n executions

## Service Management Commands

### API Management
```bash
# API logs
sudo journalctl -u claude-api -f

# API health
curl localhost:3333/health

# Restart API
sudo systemctl restart claude-api
```

### Docker Services
```bash
# Service status
docker compose -f docker-compose.brain.yml ps

# Service logs
docker compose -f docker-compose.brain.yml logs -f n8n

# Restart specific service
docker compose -f docker-compose.brain.yml up -d <service>
```

## Log Locations

| Log | Path |
|-----|------|
| Claude API | `data/logs/claude-api.log` |
| n8n | `data/logs/n8n.log` |
| n8n Events | `data/n8n/n8nEventLog*.log` (rotated) |
| Nginx | `data/nginx/data/logs/` |

## Common Issues & Solutions

### 1. n8n can't reach Claude API
**Symptom:** Telegram bot not responding, n8n workflow failures
**Solution:** Check UFW allows Docker (172.16.0.0/12) to port 3333

### 2. Telegram not responding
**Symptom:** Messages to @jarvis_momos_bot not processed
**Solution:** Check n8n workflow errors with `jarvis-status --errors`

### 3. Service down
**Symptom:** Container shows as exited or unhealthy
**Solution:** `docker compose -f docker-compose.brain.yml up -d <service>`

## Troubleshooting Workflow

1. **Quick Health Check**
   ```bash
   jarvis-status
   ```

2. **Identify Issues**
   ```bash
   jarvis-status --errors  # If issues found
   ```

3. **Deep Dive**
   ```bash
   jarvis-status --full    # For comprehensive logs
   ```

4. **Service-Specific Investigation**
   ```bash
   docker compose -f docker-compose.brain.yml logs <service>
   sudo journalctl -u claude-api -f  # For API issues
   ```

5. **Resolution Actions**
   - Restart failed containers
   - Check network connectivity
   - Verify environment variables
   - Review recent configuration changes

## When to Use This Skill

Use `/status-monitoring` when:
- Momo reports system issues
- Scheduled health checks fail
- Services appear unresponsive
- Debugging deployment problems
- Investigating performance issues
- Before and after major changes

## Integration Points

- **Telegram Bot:** Sends health alerts via `/telegram/send` endpoint
- **n8n Workflows:** Automated health monitoring triggers
- **Airtable Tasks:** Creates maintenance tasks for persistent issues
- **GitHub Issues:** Documents recurring problems for permanent fixes