Files
weave-scope/probe
Bryan Boreham 7a93c73343 Always delete container info when we get a 'destroy' event
Previously it would only delete if Docker said the container didn't
exist, which is a race between Docker sending the event and Docker
removing the info from its own records.

Extract a couple of functions to make the action clearer.
2019-05-24 16:31:42 +00:00
..
2018-10-17 19:25:12 -04:00
2018-11-13 12:51:31 +01:00
2019-04-30 19:24:23 +03:00
2018-11-13 12:51:31 +01: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.