This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| manuals:vps:traffic [2016/12/11 20:00] – toms | manuals:vps:traffic [2026/07/12 20:30] (current) – Annotate vpsAdmin navigation paths and update interface labels aither | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Data Transfers ====== | ====== Data Transfers ====== | ||
| - | Data transfers are divided into public and private. Transfers within our network are considered private | ||
| - | and do not count towards the | ||
| - | [[information: | ||
| - | node are not charged at all. | ||
| ===== Monthly Overviews ===== | ===== Monthly Overviews ===== | ||
| - | In the “Networking -> List monthly traffic” menu, we can check the monthly | + | In the “< |
| overviews of transferred data. | overviews of transferred data. | ||
| - | {{:navody:vps:datove_prenosy.png?300|}} | + | {{:en:screenshots:vpsadmin: |
| - | Under default settings, transfers for all IP addresses | + | Under default settings, transfers for all VPS for the current month are displayed. |
| - | address can appear in the overview several times since counting public and | + | |
| - | private transfers is recorded separately. | + | |
| - | Using a filter form, it is possible to only display transfers from the past, choose | + | Using a filter form, it is possible to only display transfers from the past, |
| - | between TCP, UDP or other protocols or choose a specific VPS, | + | choose a specific VPS, node, location, etc. |
| - | node, location, etc. | + | |
| ===== Real-time Transfer Monitor ===== | ===== Real-time Transfer Monitor ===== | ||
| vpsAdmin measures transferred data every 10 seconds and uses that data to calculate the average for one second. | vpsAdmin measures transferred data every 10 seconds and uses that data to calculate the average for one second. | ||
| - | You can display it either in the “Networking -> Live monitor” menu or using | + | You can display it either in the “< |
| [[manuals: | [[manuals: | ||
| ==== Web Monitor ==== | ==== Web Monitor ==== | ||
| - | {{:navody:vps:net_monitor_web.png?300|}} | + | {{:en:screenshots:vpsadmin: |
| ==== CLI Monitor ==== | ==== CLI Monitor ==== | ||
| - | [[manuals: | + | [[manuals: |
| TUI application similar to iftop | TUI application similar to iftop | ||
| < | < | ||
| - | $ vpsfreectl | + | $ vpsfreectl |
| ... | ... | ||
| -L, --list-parameters | -L, --list-parameters | ||
| Line 42: | Line 35: | ||
| --unit UNIT Select data unit (bytes or bits) | --unit UNIT Select data unit (bytes or bits) | ||
| --limit LIMIT Number of IP addresses to monitor | --limit LIMIT Number of IP addresses to monitor | ||
| - | --ip-address ADDR ADDR or ID of IP addresses to monitor | + | --user ID Filter |
| - | --ip-version VER Filter | + | --environment ID |
| - | --environment ID | + | --location ID Filter |
| - | --location ID Filter | + | --node ID Filter network |
| - | --network | + | --vps ID |
| - | --ip-range | + | --network-interface |
| - | --node ID Filter | + | -h, --help Show this message |
| - | --vps ID | + | |
| </ | </ | ||
| - | {{ :navody:vps:net_monitor_cli.png?600 |}} | + | {{ :en:screenshots:vpsadmin: |
| The program can be controlled using the arrow keys The left and right arrow keys change the column according to which | The program can be controlled using the arrow keys The left and right arrow keys change the column according to which | ||
| Line 63: | Line 55: | ||
| setting). | setting). | ||
| - | Using the '' | + | Examples: |
| - | First, display all of the possibilities: | + | |
| < | < | ||
| - | $ vpsfreectl | + | $ vpsfreectl |
| - | packets | + | |
| - | packets_in | + | |
| - | packets_out | + | |
| - | bytes | + | |
| - | bytes_in | + | |
| - | bytes_out | + | |
| - | public_packets | + | |
| - | public_packets_in | + | |
| - | public_packets_out | + | |
| - | public_bytes | + | |
| - | public_bytes_in | + | |
| - | public_bytes_out | + | |
| - | public_tcp_packets | + | |
| - | public_tcp_packets_in | + | |
| - | public_tcp_packets_out | + | |
| - | public_tcp_bytes | + | |
| - | public_tcp_bytes_in | + | |
| - | public_tcp_bytes_out | + | |
| - | public_udp_packets | + | |
| - | public_udp_packets_in | + | |
| - | public_udp_packets_out | + | |
| - | public_udp_bytes | + | |
| - | public_udp_bytes_in | + | |
| - | public_udp_bytes_out | + | |
| - | public_other_packets | + | |
| - | public_other_packets_in | + | |
| - | public_other_packets_out | + | |
| - | public_other_bytes | + | |
| - | public_other_bytes_in | + | |
| - | public_other_bytes_out | + | |
| - | private_packets | + | |
| - | private_packets_in | + | |
| - | private_packets_out | + | |
| - | private_bytes | + | |
| - | private_bytes_in | + | |
| - | private_bytes_out | + | |
| - | private_tcp_packets | + | |
| - | private_tcp_packets_in | + | |
| - | private_tcp_packets_out | + | |
| - | private_tcp_bytes | + | |
| - | private_tcp_bytes_in | + | |
| - | private_tcp_bytes_out | + | |
| - | private_udp_packets | + | |
| - | private_udp_packets_in | + | |
| - | private_udp_packets_out | + | |
| - | private_udp_bytes | + | |
| - | private_udp_bytes_in | + | |
| - | private_udp_bytes_out | + | |
| - | private_other_packets | + | |
| - | private_other_packets_in | + | |
| - | private_other_packets_out | + | |
| - | private_other_bytes | + | |
| - | private_other_bytes_in | + | |
| - | private_other_bytes_out | + | |
| - | </ | + | |
| - | Now you can display the number of packets: | + | $ vpsfreectl |
| - | + | ||
| - | < | + | |
| - | $ vpsfreectl | + | |
| </ | </ | ||
| - | |||
| - | The remaining options are used to filter the monitored IP addresses. | ||
| - | |||