Matthias Radestock 24672ed046 do not truncate tables
Limiting env vars, docker&k8s labels, and weave net connection entries
to 20 is problematic because

- the truncation is arbitrary - there is a good chance that if you
care about a specific entry it won't be there

- the truncation is not consistent - different entries get truncated
at different times

- some of the rendering logic depends on specific labels, for example
namespace filtering of containers depends on the
`io.kubernetes.pod.namespace` label.

In practice, there should never be a huge number of labels, or Weave
Net connection entries. So there is no need to truncate them.

That leaves env vars. These are of limited use, so we now omit them by
default. If they are included they are included in full, so they are
actually useful.

Fixes #3127
2018-04-12 17:13:58 +01:00
2017-12-16 23:24:22 +00:00
2017-12-15 10:27:54 +00:00
2018-04-10 10:09:33 +02:00
2017-12-11 17:02:20 +00:00
2017-01-20 14:41:36 +00:00
2018-04-12 17:13:58 +01:00
2018-04-10 13:25:54 +00:00
2018-04-12 17:13:58 +01:00
2018-03-21 10:39:54 +01:00
2017-04-27 13:52:57 +01:00
2018-03-12 15:05:22 +00:00
2018-02-05 14:29:17 +00:00
2017-10-01 09:50:41 +01:00
2017-12-27 16:34:00 +00:00
2016-04-18 10:56:33 +01:00
2017-10-13 16:12:59 -07:00
2017-08-15 12:36:43 +00:00

Weave Scope - Troubleshooting & Monitoring for Docker & Kubernetes

Circle CI Coverage Status Go Report Card Slack Status Docker Pulls GoDoc

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 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.

Extend and customize via plugins

Add custom details or interactions for your hosts, containers and/or processes by creating Scope plugins; or just choose from some that others have already written at the Github Weaveworks Scope Plugins organization.

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!

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%