Paul Bellamy a9807da0bb WIP -- deprecating host node id
It represents which probe the _thing_ was seen from, but in many cases
(container images, deployments, replicasets, services), it may have come
from several probes. We have previously conflated it to determine which
host a thing _lives on_, which it may not even have (deployments,
replica sets, services), or it may have multiple (container images).

The idea is to separate those two usages. We should convert HostNodeID
to a set of HostNodeIDs, and use that to determine which probes have
reported the thing. For determining which host a thing lives on we
should use the Parents field which we already have, but might need
extending to handle Endpoints/etc...
2016-05-12 15:28:25 +01:00
2016-05-10 09:45:29 +00:00
2016-04-21 10:04:08 +01:00
2016-02-29 15:05:19 +01:00
2016-05-11 18:08:59 +02:00
2016-04-19 15:33:26 -04:00
2016-04-19 12:15:50 +02:00
2016-05-12 15:28:25 +01:00
2016-05-12 15:28:25 +01:00
2016-05-12 15:28:25 +01:00
2016-05-11 19:06:39 +01:00
2016-05-09 09:19:11 +01:00
2016-04-21 13:48:50 +01:00
2016-05-12 09:07:59 +00:00
2016-04-18 10:56:33 +01:00
2016-04-18 10:56:33 +01:00
2016-05-10 12:41:04 +02:00
2016-05-10 20:28:52 +02:00

Weave Scope - Monitoring, visualisation & management for Docker & Kubernetes

Circle CI Coverage Status Slack Status Go Report Card

Weave Scope automatically generates a map of your application, enabling you to intuitively understand, monitor, and control your containerized, microservices based application.

Understand your Docker containers in real-time

Map you architecture

Choose an overview of your container infrastructure, or focus on a specific microservice. Easily identify and correct issues to ensure the stability and performance of your containerized applications.

Contextual details and deep linking

Focus on a single container

View contextual metrics, tags and metadata for your containers. Effortlessly navigate between processes inside your container to hosts your containers run on, arranged in expandable, sortable tables. Easily to find the container using the most CPU or memory for a given host or service.

Interact with and manage containers

Launch a command line.

Interact with your containers directly: pause, restart and stop containers. Launch a command line. All without leaving the scope browser window.

Getting started

sudo wget -O /usr/local/bin/scope https://git.io/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.)

For instructions on installing Scope on Kubernetes, DCOS or ECS, see our docs.

Getting help

If you have any questions about, feedback for or problem with Scope we invite you to:

Your feedback is always welcome!

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%