{"id":40655,"date":"2016-09-29T11:55:42","date_gmt":"2016-09-29T06:25:42","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=40655"},"modified":"2016-09-29T13:30:36","modified_gmt":"2016-09-29T08:00:36","slug":"weave-scope-monitoring-visualisation-management-for-docker","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/weave-scope-monitoring-visualisation-management-for-docker\/","title":{"rendered":"Weave Scope &#8211; Monitoring, visualisation &amp; management for Docker"},"content":{"rendered":"<p><strong>Introduction of \u00a0Weave Scope<\/strong><\/p>\n<p><strong>Weave Scope<\/strong> is a monitoring tool and visualization for\u00a0<a href=\"http:\/\/www.tothenew.com\/blog\/getting-started-with-kubernetes\/\">Kubernetes<\/a> and\u00a0<a href=\"http:\/\/www.tothenew.com\/blog\/what-is-docker-and-why-use-it\/\">Docker<\/a> . It provides a deep level view of your app as well as of your full infrastructure, which allows you to find and diagnose\u00a0any error in your distributed containerized app, in real-time. Weave Scope is use in standalone mode or in service mode. In standalone mode we deploy locally on our hosts. For now we work on standalone mode.<\/p>\n<p><strong>Installation Process<\/strong><\/p>\n<p>[js]<br \/>\nsudo curl -L git.io\/scope -o \/usr\/local\/bin\/scope<br \/>\nsudo chmod a+x \/usr\/local\/bin\/scope<br \/>\nscope launch<br \/>\n [\/js]<\/p>\n<p><strong>Features that weave scope provides<\/strong><\/p>\n<ul>\n<li><strong>Real time Container Monitoring\u00a0<\/strong><\/li>\n<\/ul>\n<p>1.Weave Scope provides a single UI to control the container life cycle across your cluster hosts. We can Start, pause, stop and restart containers from the details panel, and toggle filters for various \u00a0containers in the containers view. Scope can also attach and exec. Attach attached with the container and allows you to interact with the container. Exec runs a shell in the container so that you can do any operation in real-time. we can choose the to display the containers in the table or in the graph form. Then click on the container which you want to access:<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-40927\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope.png\" alt=\"Weave Scope\" width=\"1251\" height=\"247\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope.png 1251w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-300x59.png 300w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-1024x202.png 1024w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-624x123.png 624w\" sizes=\"(max-width: 1251px) 100vw, 1251px\" \/><\/p>\n<p>2. It open a window from where you can attach with the container , restart, pause, stop the container and execute the commands:<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-40938\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg11.png\" alt=\"Weave Scope   pnpg1\" width=\"417\" height=\"156\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg11.png 417w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg11-300x112.png 300w\" sizes=\"(max-width: 417px) 100vw, 417px\" \/><\/p>\n<p>3. clicking on the Exec shell button and it open the terminal for the container to execute the commands:<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-40939\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg2.png\" alt=\"Weave Scope   pnpg2\" width=\"790\" height=\"204\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg2.png 790w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg2-300x77.png 300w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/Weave-Scope-pnpg2-624x161.png 624w\" sizes=\"(max-width: 790px) 100vw, 790px\" \/><\/p>\n<ul>\n<li>\n<p style=\"text-align: left;\"><strong>Contextual details and Deep Linking<\/strong><\/p>\n<\/li>\n<\/ul>\n<p>Weave Scope also provides the contextual metrics, metadata and tags for our containers. It can navigate among processes inside our container to hosts our containers run on, arranged in expandable, sortable tables. It can also give options to find the container with most CPU or memory utilization:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-40675\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/dockerdeep1.png\" alt=\"dockerdeep\" width=\"1301\" height=\"635\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/dockerdeep1.png 1301w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/dockerdeep1-300x146.png 300w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/dockerdeep1-1024x499.png 1024w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/dockerdeep1-624x304.png 624w\" sizes=\"(max-width: 1301px) 100vw, 1301px\" \/><\/p>\n<ul>\n<li><strong>\u00a0Automatic Topologies and Intelligent Grouping<\/strong><\/li>\n<\/ul>\n<p>Weave scope generates a various containers, hosts and processes, showing that how they link with each other for the better <a title=\"Docker devOps\" href=\"http:\/\/www.tothenew.com\/devops-chef-puppet-docker\">understanding of your Docker<\/a> topology to control your application. It uses various established APIs (like \u00a0\/<span style=\"color: #444444; font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 24px;\"><span class=\"mceItemHidden\"><span class=\"hiddenSpellError\">proc<\/span><\/span><\/span>,the <span style=\"color: #444444; font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 24px;\"><span class=\"mceItemHidden\"><span class=\"hiddenSpellError\">Docker<\/span><\/span><\/span> API, <span style=\"color: #444444; font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14px; line-height: 24px;\"><span class=\"mceItemHidden\"><span class=\"hiddenSpellError\">conntrack<\/span><\/span><\/span> etc.) to gather information about the hosts on which scope is running. This information gathering\u00a0done without any changes into your application or needing a custom kernel module. Weave Scope probes collected the information which is used to build the topology of the containers and applications running on the hosts:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-40678\" src=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/topology.png\" alt=\"topology\" width=\"1280\" height=\"624\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2016\/09\/topology.png 1280w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/topology-300x146.png 300w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/topology-1024x499.png 1024w, \/blog\/wp-ttn-blog\/uploads\/2016\/09\/topology-624x304.png 624w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/p>\n<ul>\n<li>\u00a0 <strong>Flexible Filtering<\/strong><\/li>\n<\/ul>\n<p>A Node is filtered by its properties, such as in the Container view, they can filter by Application Containers vs System Containers or by Running vs Stopped Containers. Scope can also display various metrics such as CPU and Memory usage in the nodes, which allowing you to easily find the container using the most memory or CPU.<\/p>\n<ul>\n<li>\u00a0\u00a0<strong>Generate the Custom Metrices Using the Plugin API<\/strong><\/li>\n<\/ul>\n<p>Weave Scope\u00a0\u00a0includes a Plugin API, so that custom metrics may be generated and integrated with the Scope UI.\u00a0With the help of Scope probe plugin, we can insert custom metrics into Scope and display them together in the user interface together with the Scope\u2019s standard set of metrics.<\/p>\n<p>Hope this blog will help you to manage and monitor your docker containers in a better way.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction of \u00a0Weave Scope Weave Scope is a monitoring tool and visualization for\u00a0Kubernetes and\u00a0Docker . It provides a deep level view of your app as well as of your full infrastructure, which allows you to find and diagnose\u00a0any error in your distributed containerized app, in real-time. Weave Scope is use in standalone mode or in [&hellip;]<\/p>\n","protected":false},"author":969,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":35},"categories":[1174,2348,1],"tags":[2414,1892,1883,3965,4030,4028,4029,4027],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40655"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/969"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=40655"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40655\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=40655"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=40655"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=40655"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}