Reviewing outdated and removing obsolete images - Admin Guide (#2732)

* Remove obsolete images - Admin Guide.

* Further cleanup.

* Remove image that is not necessary.

* Formatting fix.

* Formatting fixes.

* Further cleanup.

modules/administration/pages/image-management.adoc

@@ -93,8 +93,6 @@ This section guides you through creating an ad-hoc activation key for this purpo
 To build a container, you need an activation key that is associated with a channel other than `SUSE Manager Default`.
 ====
 
-image::systems_create_activation_key.png[scaledwidth=80%]
-
 .Procedure: Creating an activation key
 . Select menu:Systems[Activation Keys].
 . Click btn:[Create Key].
@@ -488,8 +486,6 @@ Activation keys are mandatory for OS Image building.
 To build OS Images, you need an activation key that is associated with a channel other than `SUSE Manager Default`.
 ====
 
-image::systems_create_activation_key.png[scaledwidth=80%]
-
 .Procedure: Creating an activation key
 . In the {webui}, select menu:Systems[Activation Keys].
 . Click [guimenu]``Create Key``.

modules/administration/pages/live-patching-sles12.adoc

@@ -32,10 +32,7 @@ image::enable_live_patching_kgraft_install.png[scaledwidth=80%]
 .Procedure: Applying Live Patches to a Kernel
 
 . In the {productname} {webui}, select the client from menu:Systems[Overview].
-    A banner at the top of the screen shows the number of critical and non-critical packages available for the client:
-+
-image::live_patching_criticalupdates.png[scaledwidth=80%]
-
+    A banner at the top of the screen shows the number of critical and non-critical packages available for the client.
 . Click btn:[Critical] to see a list of the available critical patches.
 . Select any patch with a synopsis reading [guimenu]``Important: Security update for the Linux kernel``.
     Security bugs also include their CVE number, where applicable.

modules/administration/pages/live-patching-sles15.adoc

@@ -30,10 +30,7 @@ image::enable_live_patching_kernel_live_install.png[scaledwidth=80%]
 .Procedure: Applying Live Patches to a Kernel
 
 . In the {productname} {webui}, select the client from menu:Systems[Overview].
-    A banner at the top of the screen shows the number of critical and non-critical packages available for the client:
-+
-image::live_patching_criticalupdates.png[scaledwidth=80%]
-
+    A banner at the top of the screen shows the number of critical and non-critical packages available for the client.
 . Click btn:[Critical] to see a list of the available critical patches.
 . Select any patch with a synopsis reading [guimenu]``Important: Security update for the Linux kernel``.
     Security bugs also include their CVE number, where applicable.

modules/administration/pages/monitoring.adoc

@@ -238,9 +238,6 @@ systemctl enable --now grafana-server
     If login is successful, then you will see a prompt to change the password.
 . Click btn:[OK] on the prompt, then change your password.
 . Move your cursor to the cog icon on the side menu which will show the configuration options.
-+
-image::grafana_sidemenu_datasource.png[scaledwidth=40%]
-
 . Click btn:[Data sources].
 . Click btn:[Add data source] to see a list of all supported data sources.
 . Choose the Prometheus data source.
@@ -254,8 +251,8 @@ image::monitoring_grafana_example.png[scaledwidth=80%]
 
 [NOTE]
 ====
-. For more information about the monitoring formulas, see xref:specialized-guides:salt/salt-formula-monitoring.adoc[].
-. For more information on how to manually install and configure Grafana, see https://grafana.com/docs.
+* For more information about the monitoring formulas, see xref:specialized-guides:salt/salt-formula-monitoring.adoc[].
+* For more information on how to manually install and configure Grafana, see https://grafana.com/docs.
 ====
 
 == Configure {productname} Monitoring
@@ -297,10 +294,8 @@ The exporter packages are pre-installed in {productname} Server and Proxy, but t
 . Click btn:[Enable services].
 . Restart Tomcat and Taskomatic.
 . Navigate to the URL of your Prometheus server, on port 9090 (for example, [literal]``http://example.com:9090``)
-. In the Prometheus UI, navigate to menu:[Status > Targets] and confirm that all the endpoints on the ``mgr-server`` group are up.
-. If you have also installed Grafana with the {webui}, the server insights are visible on the {productname} Server dashboard.
-
-image::monitoring_enable_services.png[scaledwidth=80%]
+. In the Prometheus UI, navigate to menu:Status[Targets] and confirm that all the endpoints on the ``mgr-server`` group are up.
+. If you have also installed Grafana with the {webui}, the server insights are visible on the {productname} Server dashboard, in the menu:Admin[Manager Configuration > Monitoring].
 
 [IMPORTANT]
 ====
@@ -478,7 +473,7 @@ If you have configured your monitoring server with the {webui}, metrics collecti
 
 .Procedure: Configuring Prometheus Exporters on a Client
 
-. In the {productname} {webui}, open the details page of the client to be monitored, and navigate to the menu:Formulas tab.
+. In the {productname} {webui}, open the details page of the client to be monitored, and navigate to the menu:Formulas[] tab.
 . Check the [guimenu]``Enabled`` checkbox on the ``Prometheus Exporters`` formula.
 . Click btn:[Save].
 . Navigate to the menu:Formulas[Prometheus Exporters] tab.
@@ -487,8 +482,6 @@ If you have configured your monitoring server with the {webui}, metrics collecti
 . Click btn:[Save Formula].
 . Apply the highstate.
 
-image::monitoring_configure_formula.png[scaledwidth=80%]
-
 [NOTE]
 ====
 Monitoring formulas can also be configured for System Groups, by applying the same configuration used for individual systems inside the corresponding group.