Files
3m-ui/docs/node-traffic.md
T
kazeyukiro e89750f9d0 docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
docs: align README/OpenAPI with per-node traffic, limits, backups
- docs/node-traffic.md; feature tables; installation backup cleanup note
- OpenAPI: traffic_multiplier, GET /users/{id}/node-traffic
2026-09-20 23:55:00 +08:00

33 lines
1.2 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Per-node traffic & multiplier
## Concepts
| Term | Meaning |
|------|---------|
| **Raw** | Real upload/download on that listener for the user |
| **Multiplier** | Listener field `traffic_multiplier` (default **1**, range about 0.01–100) |
| **Billed** | `raw × multiplier` — this is what is added to the user’s `traffic_used` quota |
Example: multiplier `1.5`, 100 MiB raw → **150 MiB** counted against the user limit.
## Where to configure
- **Nodes (Listeners)** → edit node → **Traffic multiplier**
- **Users** → node-traffic action (chart icon) → per-node table (raw + billed)
## API
```http
GET /api/v1/users/{id}/node-traffic
```
Response items include `upload_bytes`, `download_bytes`, `traffic_used` (raw), `multiplier`, `billed_upload`, `billed_download`, `billed_used`.
Listener create/update accepts `traffic_multiplier` (omit or `≤0` → treated as `1`).
## Notes
- Attribution uses Mihomo connection `inboundName` ↔ listener **name**.
- Resetting user traffic (single, batch, monthly, or cycle reset) clears per-node rows for that scope.
- Historical traffic from before this feature only exists as the user total; new usage is split by node going forward.