explaingit

weaveworks/scope

5,913GoAudience · ops devopsComplexity · 3/5LicenseSetup · easy

TLDR

An archived container monitoring tool that showed a live browser map of your Docker or Kubernetes infrastructure, letting you inspect metrics and manage containers without leaving the UI.

Mindmap

mindmap
  root((repo))
    What it does
      Live container map
      Real-time metrics
      Browser interface
    Actions
      Pause containers
      Open terminal
      Restart services
    Tech
      Go
      Docker
      Kubernetes
    Status
      Archived
      Apache 2.0
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

View a live visual map of all running containers and the network connections between them

USE CASE 2

Check CPU and memory usage of individual containers directly from a browser tab

USE CASE 3

Open a terminal session inside a running container without leaving the web interface

USE CASE 4

Embed Scope as a monitoring component inside a downstream product or internal tool

Tech stack

GoDockerKubernetes

Getting it running

Difficulty · easy Time to first run · 30min

Project is archived and no longer maintained, suitable only for reference or embedding in internal tooling, not for new production deployments.

Apache 2.0, use freely for any purpose, including commercial use, with attribution.

In plain English

Weave Scope was a monitoring and visualization tool for applications running in Docker containers or on Kubernetes. It automatically generated a live map of your running containers and the connections between them, letting you see your entire infrastructure in a browser without manual configuration. The tool gave you a real-time view of what was running, with the ability to drill down into individual containers, see CPU and memory usage, and jump between related processes and hosts. Beyond just viewing, it let you take action directly from the browser: you could pause, restart, or stop containers, and open a terminal session inside one, all without leaving the interface. Scope also supported a plugin system, so teams could add custom metrics or controls for their specific services. Several organizations used it in production, including as a component inside other products built by companies like Deepfence and MayaData. However, this project is no longer maintained. Weaveworks, the company that built it, ended the Weave Cloud service. The repository is archived and the README explicitly states it will not receive further updates. The code remains publicly available under the Apache 2.0 license, and some companies have continued using it as a component inside their own products, but there is no active development community or support. If you are looking for a currently maintained container monitoring solution, you would need to look elsewhere. For historical reference or internal use in a downstream product, the code is available and can be run by downloading and launching a Docker image with a single script.

Copy-paste prompts

Prompt 1
How do I run Weave Scope with a single Docker command to visualize my running containers?
Prompt 2
Show me how to connect Weave Scope to a Kubernetes cluster and view pod-to-pod connections
Prompt 3
How do I use the Weave Scope plugin system to add a custom metric panel for my service?
Prompt 4
What is the quickest way to open a shell inside a running container using Weave Scope?
Open on GitHub → Explain another repo

← weaveworks on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.