mirror of
https://github.com/oneclickvirt/oneclickvirt.github.io.git
synced 2026-05-23 10:21:29 +08:00
Clarify traffic statistics limitations in usage guide
Add note about flawed current traffic statistics.
This commit is contained in:
@@ -142,6 +142,8 @@ It is not recommended to modify the mapping method unless you know what this set
|
||||
|
||||
Literal meaning. Set the maximum bandwidth and available traffic total calculated by natural month for instances created on the node. Traffic monitoring and traffic statistics are automatically enabled by default.
|
||||
|
||||
(Current traffic statistics are flawed, as they cannot distinguish between public and internal network traffic, leading to inflated and inaccurate figures. Do not enable.)
|
||||
|
||||
When instance traffic exceeds the node limit or user limit, the instance will be automatically stopped; when the node's total traffic is exceeded, all instances on the entire node will be stopped.
|
||||
|
||||
At the beginning of the month, statistics data will be reset, and all instances that were automatically stopped due to reaching traffic limits will be restarted.
|
||||
@@ -467,4 +469,4 @@ Detailed configuration for system log recording, based on the zap log library.
|
||||
- `show-line`: Whether to display the filename and line number of the log call
|
||||
- `stacktrace-key`: Key name for stack trace information
|
||||
|
||||
Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.
|
||||
Note: When debugging issues, `level` should be set to `debug` to obtain detailed log information.
|
||||
|
||||
Reference in New Issue
Block a user