Matthias Radestock
15b605f804
...when 'Hide Unconnected' is selected, which is the default. Here's the problem... The connectedness filter looks for `is_connected` marks in the Latest map of the nodes. The mark is added by ColorConnected, which is invoked by ProcessRenderer. That in turn is the base renderer for ProcessNameRenderer, which is what the process-by-name view renders. However, the process2Names mapping does not propagate any metadata, hence there are no `is_connected` marks on the result nodes. Consequently they are all filtered out. The problem was introduced in #3009, when I added the ability for users to chose whether to show or hide unconnected processes (previously unconnected processes were always hidden) - looks like I failed to check that the process-by-name view was working with the new filter. Oops. The fix is to move the ColorConnected call from ProcessRenderer to the higher-level renderers - ProcessWithContainerNameRenderer (which is what the 'Processes' view renders) and ProcessNameRenderer. This has the beneficial side effect of improving performance for other renderers which invoke ProcessRenderer, none of which need connectedness-coloring. Fixes #3205
Weave Scope - Troubleshooting & Monitoring for Docker & Kubernetes
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
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
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
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:
- Read the Weave Scope docs.
- Invite yourself to the Weave community slack.
- Ask a question on the #scope slack channel.
- Join the Weave User Group and get invited to online talks, hands-on training and meetups in your area.
- Send an email to Scope community group.
- Join (and read up on) the regular Scope community meetings.
- File an issue.
Your feedback is always welcome!