Files
weave-scope/probe
gotjosh beeb27810c Add tests for probe/cri/registry
Unhappy path tests try to cover three scenarios:

- When the endpoint URL scheme is not explicitly supported e.g. HTTP
- When the endpoint URL scheme is TCP which is also not supported
- When the fail to parse the given URL (to extract the scheme)

The happy path covers two scenarios:

- When we specify the supported scheme in the URL which is an unix
socket e.g. unix///var/run/dockershim.sock
- When we pass a socket address but fail to specify the scheme but our registry attempts
to use the fallback protocol e.g. var/run/dockershim.sock
2018-11-01 20:17:03 +00:00
..
2018-11-01 20:17:03 +00:00
2018-10-11 17:54:29 +00:00
2018-10-09 14:32:02 +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.