Mike Lang eb0298b9d5 report: Refactor various methods to avoid explicitly listing topologies
By reducing the number of times we refer to every topology by name line by line,
we make it easier to add new topologies, reduce the risk of bugs where a topology is not listed,
and reduce the risk of the repeated lines getting out of sync with each other.

We introduce two new methods to assist this:
	WalkPairedTopologies, a modified WalkTopologies that gives the called function
		the same topology from two reports. This is used, for example, to implement Copy and Merge.
	TopologyMap, which returns a map of all topologies by name. This is then used to implement all other methods.

This leaves only 4 instances of listing topologies:
	In the consts at the top of the file, to give it a name
	In the struct itself
	In the constructor, where we need to set per-topology settings
	In TopologyMap
2017-03-30 16:38:34 -07:00
2017-03-27 12:55:34 -07:00
2017-02-27 17:49:26 +01:00
2017-03-17 13:20:06 +00:00
2017-01-20 14:41:36 +00:00
2016-04-19 12:15:50 +02:00
2017-03-21 14:42:34 +01:00
2017-03-29 15:57:25 +02:00
2017-02-27 17:49:26 +01:00
2017-03-27 13:54:04 -07:00
2017-03-27 08:13:58 -07:00
2016-04-18 10:56:33 +01:00
2017-03-25 10:49:40 -07:00
2016-04-18 10:56:33 +01:00

Weave Scope - Troubleshooting & Monitoring for Docker & Kubernetes

Circle CI Coverage Status Go Report Card Slack Status Docker Pulls

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 curl -L git.io/scope -o /usr/local/bin/scope
sudo chmod a+x /usr/local/bin/scope
scope launch

This script downloads and runs a recent Scope image from 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 the docs.

Getting help

If you have any questions about, feedback for or problems with Scope:

Your feedback is always welcome!

S
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%