console

Author: pwright

input/console/index.md

@@ -15,7 +15,7 @@ The Network console provides data and visualizations of the traffic flow between
 
 1. Determine which site in your network is best to enable the Network console using the following criteria:
 
-   * Does the service network cross a firewall? For example, if you want the console to be available only inside the firewall, you need to locate the Network console on a site inside the firewall.
+   * Does the application network cross a firewall? For example, if you want the console to be available only inside the firewall, you need to locate the Network console on a site inside the firewall.
    * Is there a site that processes more traffic than other sites? For example, if you have a frontend component that calls a set of services from other sites, it might make sense to locate the Network console on that site to minimize data traffic.
    * Is there a site with more or cheaper resources that you want to use? For example, if you have two sites, A and B, and resources are more expensive on site A, you might want to locate the Network console on site B.
 

input/index.html.in

@@ -86,4 +86,17 @@ body_template: config/wide-body.html
       <li><a href="https://skupperproject.github.io/refdog/resources/index.html">YAML reference</a></li>
     </nav>
   </div>
+</div>
+
+<div class="columns">
+
+  <div>
+    <h2 id="observability">Observability</h2>
+    <p>Learn how to monitor traffic using the Skupper console.</p>
+    <nav>
+      <li><a href="./console/index.html">Using the Skupper console</a></li>
+      
+    </nav>
+  </div>
+
 </div>

input/kube-cli/site-configuration.md

@@ -3,7 +3,7 @@
 
 Using the skupper command-line interface (CLI) allows you to create and manage sites from the context of the current namespace.
 
-A typical workflow is to create a site, link sites together, and expose services to the service network.
+A typical workflow is to create a site, link sites together, and expose services to the application network.
 
 <a id="kube-checking-cli"></a>
 ## Checking the Skupper CLI

input/kube-yaml/site-configuration.md

@@ -3,7 +3,7 @@
 
 Using YAML allows you to create and manage sites from the context of the current namespace.
 
-A typical workflow is to create a site, link sites together, and expose services to the service network.
+A typical workflow is to create a site, link sites together, and expose services to the application network.
 
 <a id="kube-creating-simple-site-yaml"></a>
 ## Creating a simple site on Kubernetes using YAML

input/overview/load-balancing.md

@@ -1,12 +1,12 @@
 <a id="overview-load-balancing"></a>
 # Skupper load balancing and failover
 
-Skupper enables load balancing and failover across servers located across the service network.
+Skupper enables load balancing and failover across servers located across the application network.
 Specifically, Skupper balances **active TCP connections** across workloads deployed in distinct sites.
 If a workload at one site becomes unavailable, traffic is automatically rerouted to available sites. 
-For example, if you deploy the same backend code on two sites and expose the backend on the service network, concurrent requests from a third site to the backend service are processed by both sites.
+For example, if you deploy the same backend code on two sites and expose the backend on the application network, concurrent requests from a third site to the backend service are processed by both sites.
 
-In a service network, the routing algorithm attempts to use the path with the lowest total **cost** from client to target server.
+In an application network, the routing algorithm attempts to use the path with the lowest total **cost** from client to target server.
 
 **Understanding link cost**
 

input/system-cli/site-configuration.md

@@ -3,7 +3,7 @@
 
 Using the skupper command-line interface (CLI) allows you to create and manage Skupper sites from the context of the current user.
 
-A typical workflow is to create a site, link sites together, and expose services to the service network.
+A typical workflow is to create a site, link sites together, and expose services to the application network.
 
 A *local system* includes Docker, Podman or Linux system.
 

input/system-yaml/site-configuration.md

@@ -3,7 +3,7 @@
 
 Using YAML allows you to create and manage sites on Docker, Podman and Linux.
 
-A typical workflow is to create a site, link sites together, and expose services to the service network.
+A typical workflow is to create a site, link sites together, and expose services to the application network.
 
 If you require more than one site, specify a unique namespace when using  `skupper`, for example `skupper --namespace second-site ...`.