Files
weave-scope/probe
Bryan Boreham fc46ea17ee refactor(probe/ebpf): track connections by four-tuple+namespace
The previous code tracked only by four-tuple, which meant that two
connections with same address/port combinations in different namespace
would clash and one would get dropped.

Also previously the tuple was duplicated between the map key and
value, so we remove it from the value.

We only add the namespace in the case that the local address is
loopback, which matches how the rest of Scope treats addresses.
2020-01-13 08:53:47 +00:00
..
2018-02-15 10:36:49 +00:00

Quick overview

Information gatherers

These implement the Reporter interface

  • awsecs Deals with talking to AWS ECS to get stats and info
  • docker Inspects the docker status
  • endpoint Gathers connection data
  • host Gets data from the host os, including things like CPU and mem stats
  • kubernetes Gathers data from k8s
  • overlay Talks to Weave Net for network stats from the overlay network
  • process Is code that looks up running process and stats form the os

Utility and control

  • appclient Deals with generating and sending reports
  • controls Utility code for control messages and the like
  • plugins allows plugins to be added to the probe.