Tom Wilkie b9e968ff43 Cache the walk of the process tree, reusing it in docker tagger and process reporter.
Update the cache every spy tick.

This change make CPU usage of scope on my box go from ~40% to ~17%.
2015-06-29 11:16:38 +00:00
2015-06-24 14:01:17 +00:00
2015-06-24 14:01:17 +00:00
2015-06-24 09:51:29 +00:00
2015-06-24 14:01:17 +00:00
2015-06-15 12:49:47 +02:00
2015-05-19 10:02:02 +00:00
2015-05-19 10:02:55 +00:00
2015-06-01 20:50:52 +02:00
2015-06-23 14:29:54 +00:00

Scope

Circle CI Coverage Status Sourcegraph

Weave Scope Screenshot

Overview

Weave Scope automatically generates a map of your containers, enabling you to intuitively understand, monitor, and control your applications.

Please note that the code, and especially the building and running story, is in a prerelease state. Please take a look, but don't be surprised if you hit bugs or missing pieces.

Getting started

sudo wget -O /usr/local/bin/scope \
  https://github.com/weaveworks/scope/releases/download/latest_release/scope
sudo chmod a+x /usr/local/bin/scope
sudo scope launch

This script will download and run a recent Scope image from the Docker Hub. Now, open your web browser to http://localhost:4040. (If you're using boot2docker, replace localhost with the output of boot2docker ip.)

Build

make

This will produce a Docker image called weaveworks/scope.

Note that the repository contains a copy of the compiled UI. To build a fresh UI from the source in the client subdirectory, and re-build the Docker container,

make scope_ui_build.tar
make static
make

Run

./scope launch
Description
Monitoring, visualisation & management for Docker & Kubernetes
Readme Pixar 103 MiB
Languages
Go 60.9%
JavaScript 28.3%
Shell 6.7%
Python 1.6%
HCL 1%
Other 1.5%