diff --git a/README.md b/README.md
index 10033f5f6..b86961b40 100644
--- a/README.md
+++ b/README.md
@@ -48,7 +48,7 @@ That launches my 'kamel' process from an XML file in the directory of the file (
 There are two types of "output channels" providing details for the extension.
 
 * The "Camel-K" output channel (View->Output, select "Camel-K" from the drop-down in the view) offers details about events such as when the Camel-K Integrations view is refreshed, when new integrations are started, when running integrations are stopped, and when the log of a particular running integration is viewed.
-* In that last case, the "View log for Camel-K Integration" menu, when invoked on a running integration in the Camel-K Integrations view, opens a new Output channel named for the running "pod" associated with that particular integration. This gives you access to the running Camel log for the selected integration.
+* In that last case, the "Follow log for Camel-K Integration" menu, when invoked on a running integration in the Camel-K Integrations view, opens a new Output channel named for the running "pod" associated with that particular integration. This gives you access to the running Camel log for the selected integration.
 
 ## Stopping running Camel-K integrations
 
@@ -58,11 +58,17 @@ Once an integration is running, it may be stopped in the "Camel-K Integrations"
 
 ## Camel-K Integrations view
 
-The Camel-K Integrations view offers a list of the "integrations" registered with the current Camel-K context. If you right-click on a running integration, you can "Remove" an integration to stop them in the system.
+The Camel-K Integrations view offers a list of the "integrations" registered with the current Camel-K context. If you right-click on a running integration, you can "Remove" an integration to stop them in the system or "Follow" the log to show the running log for your integration in a new Output channel.
 
 ![Camel-K integrations view Remove](images/camelk-integrations-view-remove-menu.jpg)
 
-The view has a "Refresh" button that can be used to manually trigger a refresh of the list, but when you add/remove file-based integrations in the Explorer view, it should refresh automatically.
+Following a log opens a new Output channel named for the running Kubernetes pod where the integration is running. It updates as new data is added to it:
+
+![Camel-K integrations view Log](images/camelk-integrations-view-integrations-log.jpg)
+
+In addition, the view has a "Refresh" button that can be used to manually trigger a refresh of the list, but when you add/remove file-based integrations in the Explorer view, it should refresh automatically.
+
+Note: Refreshing the view sometimes is delayed as we wait for pods to start. You may need to give it a few seconds. If nothing happens, the Refresh button is a good option.
 
 ![Camel-K integrations view Refresh](images/camelk-integrations-view-refresh-action.jpg)
 
diff --git a/images/camelk-integrations-view-integrations-log.jpg b/images/camelk-integrations-view-integrations-log.jpg
new file mode 100644
index 000000000..4fee7d99a
Binary files /dev/null and b/images/camelk-integrations-view-integrations-log.jpg differ
diff --git a/images/camelk-integrations-view-remove-menu.jpg b/images/camelk-integrations-view-remove-menu.jpg
index dd0359074..02693f829 100644
Binary files a/images/camelk-integrations-view-remove-menu.jpg and b/images/camelk-integrations-view-remove-menu.jpg differ
diff --git a/images/kubernetes-view-camelk-run-xml-menu.jpg b/images/kubernetes-view-camelk-run-xml-menu.jpg
index 3d730a680..e23a8760b 100644
Binary files a/images/kubernetes-view-camelk-run-xml-menu.jpg and b/images/kubernetes-view-camelk-run-xml-menu.jpg differ
diff --git a/package-lock.json b/package-lock.json
index f2729c0a9..44f3c159d 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -94,6 +94,7 @@
             "version": "10.0.3",
             "resolved": "https://registry.npmjs.org/@types/nock/-/nock-10.0.3.tgz",
             "integrity": "sha512-OthuN+2FuzfZO3yONJ/QVjKmLEuRagS9TV9lEId+WHL9KhftYG+/2z+pxlr0UgVVXSpVD8woie/3fzQn8ft/Ow==",
+            "dev": true,
             "requires": {
                 "@types/node": "*"
             }
@@ -653,8 +654,7 @@
         "lodash": {
             "version": "4.17.11",
             "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.11.tgz",
-            "integrity": "sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg==",
-            "dev": true
+            "integrity": "sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg=="
         },
         "lolex": {
             "version": "4.0.1",