History

kongfei 2768920249 change build tag		2022-08-16 09:24:47 +08:00
..
README.md	update readme of ipvs	2022-08-15 21:26:24 +08:00
ipvs.go	change build tag	2022-08-16 09:24:47 +08:00
ipvs_linux_amd64.go	delete instance from ipvs plugin	2022-08-15 20:00:42 +08:00

README.md

ipvs

Forked from telegraf. The IPVS input plugin uses the linux kernel netlink socket interface to gather metrics about ipvs virtual and real servers. Supported Platforms: Linux

Permissions

Assuming you installed the telegraf package via one of the published packages, the process will be running as the telegraf user. However, in order for this plugin to communicate over netlink sockets it needs the telegraf process to be running as root (or some user with CAP_NET_ADMIN and CAP_NET_RAW). Be sure to ensure these permissions before running telegraf with this plugin included.

Configuration

# Collect virtual and real server stats from Linux IPVS
  # no configuration

Metrics

Server will contain tags identifying how it was configured, using one of address + port + protocol OR fwmark. This is how one would normally configure a virtual server using ipvsadm.

ipvs_virtual_server
- tags:
  - sched (the scheduler in use)
  - netmask (the mask used for determining affinity)
  - address_family (inet/inet6)
  - address
  - port
  - protocol
  - fwmark
- fields:
  - connections
  - pkts_in
  - pkts_out
  - bytes_in
  - bytes_out
  - pps_in
  - pps_out
  - cps
ipvs_real_server
- tags:
  - address
  - port
  - address_family (inet/inet6)
  - virtual_address
  - virtual_port
  - virtual_protocol
  - virtual_fwmark
- fields:
  - active_connections
  - inactive_connections
  - connections
  - pkts_in
  - pkts_out
  - bytes_in
  - bytes_out
  - pps_in
  - pps_out
  - cps

Example Output

Virtual server is configured using fwmark and backed by 2 real servers:

ipvs_virtual_server,address=172.18.64.234,address_family=inet,netmask=32,port=9000,protocol=tcp,sched=rr bytes_in=0i,bytes_out=0i,pps_in=0i,pps_out=0i,cps=0i,connections=0i,pkts_in=0i,pkts_out=0i 1541019340000000000
ipvs_real_server,address=172.18.64.220,address_family=inet,port=9000,virtual_address=172.18.64.234,virtual_port=9000,virtual_protocol=tcp active_connections=0i,inactive_connections=0i,pkts_in=0i,bytes_out=0i,pps_out=0i,connections=0i,pkts_out=0i,bytes_in=0i,pps_in=0i,cps=0i 1541019340000000000
ipvs_real_server,address=172.18.64.219,address_family=inet,port=9000,virtual_address=172.18.64.234,virtual_port=9000,virtual_protocol=tcp active_connections=0i,inactive_connections=0i,pps_in=0i,pps_out=0i,connections=0i,pkts_in=0i,pkts_out=0i,bytes_in=0i,bytes_out=0i,cps=0i 1541019340000000000

Virtual server is configured using proto+addr+port and backed by 2 real servers:

ipvs_virtual_server,address_family=inet,fwmark=47,netmask=32,sched=rr cps=0i,connections=0i,pkts_in=0i,pkts_out=0i,bytes_in=0i,bytes_out=0i,pps_in=0i,pps_out=0i 1541019340000000000
ipvs_real_server,address=172.18.64.220,address_family=inet,port=9000,virtual_fwmark=47 inactive_connections=0i,pkts_out=0i,bytes_out=0i,pps_in=0i,cps=0i,active_connections=0i,pkts_in=0i,bytes_in=0i,pps_out=0i,connections=0i 1541019340000000000
ipvs_real_server,address=172.18.64.219,address_family=inet,port=9000,virtual_fwmark=47 cps=0i,active_connections=0i,inactive_connections=0i,connections=0i,pkts_in=0i,bytes_out=0i,pkts_out=0i,bytes_in=0i,pps_in=0i,pps_out=0i 1541019340000000000