Matthias Radestock 21b3bcabe7 in target.Merge(arg), always merge arg into target
That way, as the top-level target.Merge(arg) on Report recursively
descends into the data structure, all component Merge operations are
invoked as target_component.Merge(arg_component).

Merge is commutative, so semantically this does not matter. But it is
easier to reason about and debug Merge code this way.

Moreover, the merge order matters for performance since some merges, in
particular LatestMap.Merge, are faster when the entries in the target
are younger than the entries in the arg. So this change allows
high-level code to invoke Report.Merge in the optimal order, in the
knowledge that the order is preserved for component merges.

Most of the Merge functions were already preserving order. Of the four
that didn't, Nodes.Merge is the most significant - it is the only one
that affects LatestMap.Merge order.
2016-08-14 20:42:54 +01:00
2016-07-12 14:22:09 +01:00
2016-02-29 15:05:19 +01:00
2016-04-19 12:15:50 +02:00
2016-08-11 15:41:07 +00:00
2016-08-14 17:19:03 +01:00
2016-07-14 15:26:34 +01:00
2016-08-05 15:04:52 +00:00
2016-04-18 10:56:33 +01:00
2016-07-12 14:22:09 +01:00
2016-04-18 10:56:33 +01:00

Weave Scope - Monitoring, visualisation & management 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 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 the docs.

Getting help

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

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%