> For the complete documentation index, see [llms.txt](https://docs.hipersnipe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hipersnipe.com/for-operators/monitoring.md).

# Monitoring and logs

## Log files

| File           | Contents                                                |
| -------------- | ------------------------------------------------------- |
| `bot.log`      | All bot + limit engine output (UTF-8, flushed per line) |
| `security.log` | Security telemetry events only                          |

## Log format

```
HH:MM:SS | LEVEL    | logger_name | message
```

## Key log patterns

| Pattern                                           | Meaning                              |
| ------------------------------------------------- | ------------------------------------ |
| `Update id=... is handled`                        | Telegram callback processed          |
| `UI SPEED: Total: Xms`                            | Trading UI render timing             |
| `[ORACLE] Skipped execution due to http_fallback` | WSS stale; shield/limit skipped      |
| `[METRICS] WSS Health`                            | Active subscriptions healthy         |
| `PnL CALC failed`                                 | PnL replay error (check trades JSON) |
| `roi challenge broadcast`                         | Tournament leaderboard posted        |

## systemd journal

```bash
sudo journalctl -u solana-bot -f -n 100
```

## Log level

Set in `.env`:

```
LOG_LEVEL=DEBUG
```

Use DEBUG only when diagnosing—verbose RPC traces increase disk I/O.

## Health indicators

| Check           | Command / location             |
| --------------- | ------------------------------ |
| Process running | `systemctl status solana-bot`  |
| WSS active      | `[METRICS] WSS Health` in logs |
| DB writable     | No `database is locked` spam   |
| RPC healthy     | No sustained 429 errors        |

## Disk space

`bot.log` grows unbounded. Rotate with logrotate:

```
/path/to/bot.log {
    daily
    rotate 14
    compress
    missingok
    copytruncate
}
```

## Alerts (recommended)

Set up external monitoring for:

* Process down (systemd restart loop)
* Disk > 80%
* Error rate spike in `security.log`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hipersnipe.com/for-operators/monitoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.