-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GITBOOK-317: change request with no subject merged in GitBook
- Loading branch information
1 parent
84d9075
commit fd069de
Showing
2 changed files
with
14 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# How do VPN statistics work | ||
|
||
1. Each defguard gateway reads kernel data from the WireGuard® interface for each peer. | ||
2. If any change is detected between previous stats (bytes in/out) then through the gRPC interface the gateway sends those statistics to defguard core. | ||
|
||
{% hint style="info" %} | ||
If the gateway doesn't detect any changes in stats, doesn't send anything to core. | ||
|
||
The period for each gateway to gather stats from the interfaces is defined by `DEFGUARD_STATS_PERIOD` ENV value (or -p argument) - default 30sec. | ||
{% endhint %} | ||
|
||
3. Core stores all the data send trough gRPC in the database (table `wireguard_peer_stats`). | ||
4. Then when displaying the VPN overview does all the calculations and aggregations of the data to display them. |