add log subsection
Change-Id: I564f9e70193a8db61920af6b58d6d7bf066171ea
diff --git a/onramp/figures/k9s.png b/onramp/figures/k9s.png
new file mode 100644
index 0000000..9064e91
--- /dev/null
+++ b/onramp/figures/k9s.png
Binary files differ
diff --git a/onramp/inspect.rst b/onramp/inspect.rst
index 7c1f17a..de56601 100644
--- a/onramp/inspect.rst
+++ b/onramp/inspect.rst
@@ -1,12 +1,13 @@
Closer Look
---------------
-Before tearing down your Quick Start deployment, there are two
+Before tearing down your Quick Start deployment, there are three
additional steps you can take to watch Aether in action. The first is
to bring up the Aether Management Plane (AMP), which includes
-Dashboards showing different aspects of Aether's runtime behavior. The
-second is to enable packet capture, and then run an analysis tool to
-trace the flow of packets into and out of SD-Core.
+Dashboards showing different aspects of Aether's runtime behavior.
+The second is to inspect the logs written by the various microservices.
+The third is to enable packet capture, and then run an analysis
+tool to trace the flow of packets into and out of SD-Core.
Install AMP
@@ -87,6 +88,45 @@
$ make aether-amp-uninstall
+Viewing Logs
+~~~~~~~~~~~~~~~~
+
+You've already seen the log file generated by gNBsim for each
+emulation run, but you can also inspect the logs generated by
+individual microservices that implement Aether. Doing so is certainly
+helpful when debugging a failure, but it can also be an aid in
+learning how each microservice works. For example, the following
+command outputs the log for the ``bessd`` container, one of five
+containers running as part of the ``upf-0`` pod:
+
+.. code-block::
+
+ $ kubectl logs -n omec -p upf-0 bessd
+
+While ``kubectl`` works just fine for tasks like this, you may also
+want to install `k9s <https://k9scli.io/>`__\ , a terminal-based UI
+that provides a convenient alternative for interacting with Kubernetes.
+Once installed, the following command brings up the UI for the OMEC
+namespace that implements SD-Core.
+
+.. code-block::
+
+ $ k9s -n omec
+
+:numref:`Figure %s <fig-k9s>` shows an example k9s display, where you
+can scroll up and down, and then invoke one of the listed
+commands—such as ``<l>`` (display log) or ``<s>`` (open a shell)—for
+the selected pod.
+
+.. _fig-k9s:
+.. figure:: figures/k9s.png
+ :width: 700px
+ :align: center
+
+ Screenshot of k9s's UI for the OMEC namespace, with the AMF pod
+ currently selected.
+
+
Run Ksniff and Wireshark
~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/onramp/start.rst b/onramp/start.rst
index 01d2eb0..54be6ca 100644
--- a/onramp/start.rst
+++ b/onramp/start.rst
@@ -233,10 +233,7 @@
If you are not familiar with ``kubectl`` (the CLI for Kubernetes), we
recommend that you start with `Kubernetes Tutorial
-<https://kubernetes.io/docs/tutorials/kubernetes-basics/>`__. And
-although not required, you may also want to install
-`k9s <https://k9scli.io/>`__\ , a terminal-based UI that provides a
-convenient alternative to ``kubectl`` for interacting with Kubernetes.
+<https://kubernetes.io/docs/tutorials/kubernetes-basics/>`__.
Note that we have not yet installed Kubernetes or Helm, so these
commands are not yet available. At this point, the only verification
