Rephrase backend widget status (#4418)

maximiliankolb · maximiliankolb · commit 27b1a9528319 · 2025-11-18T11:41:52.000+01:00
* Fix status of services procedure in WebUI Katello 4.18+ does not provide the Backend System Status widget anymore. The code was moved to Foreman and will be part of Foreman 4.17+. Refs PR 11473 in katello Refs PR 10651 in foreman Refs Redmine issue 38667 (Extend Backend system status widget) Refs Redmine issue 38668 (Remove Backend System Status widget) * Split viewing status by interface * Document Backend system status widget Tested on Foreman 3.16.1 and Katello 4.18.1 (cherry picked from commit 42f56c6)
diff --git a/guides/common/assembly_disaster-recovery-by-virtualizing-your-projectserver.adoc b/guides/common/assembly_disaster-recovery-by-virtualizing-your-projectserver.adoc
@@ -8,4 +8,4 @@ include::modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-proje
 
 include::modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]
diff --git a/guides/common/assembly_disaster-recovery-for-active-and-passive-project-server-with-external-storage.adoc b/guides/common/assembly_disaster-recovery-for-active-and-passive-project-server-with-external-storage.adoc
@@ -8,4 +8,4 @@ include::modules/proc_preparing-for-disaster-recovery-with-active-and-passive-pr
 
 include::modules/proc_recovering-from-disaster-with-active-and-passive-project-server-with-external-storage.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]
diff --git a/guides/common/assembly_disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc b/guides/common/assembly_disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc
@@ -8,6 +8,6 @@ include::modules/proc_preparing-for-disaster-recovery-with-active-and-passive-pr
 
 include::modules/proc_recovering-from-disaster-with-active-and-passive-project-server-and-backup-and-restore.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]
 
 include::modules/ref_example-of-a-weekly-full-backup-followed-by-daily-incremental-backups.adoc[leveloffset=+1]
diff --git a/guides/common/assembly_logging-and-reporting-problems.adoc b/guides/common/assembly_logging-and-reporting-problems.adoc
@@ -40,7 +40,7 @@ include::modules/proc_selective-debugging-with-individual-loggers.adoc[leveloffs
 
 include::modules/ref_overview-of-individual-loggers.adoc[leveloffset=+1]
 
-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]
+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]
 
 include::modules/proc_restarting-services.adoc[leveloffset=+1]
 
diff --git a/guides/common/modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-projectserver.adoc b/guides/common/modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-projectserver.adoc
@@ -25,5 +25,5 @@ While snapshots provide quick recovery points, backing up your snapshots gives y
 . Verify that your hypervisor takes the snapshots according to the schedule that you defined.
 . Use the latest snapshot of your {ProjectServer} and restore it in an isolated environment.
 . To verify that you will be able to restore {Project} services in case of a disaster, assess the functionality of the test {ProjectServer}.
-See xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
 . Perform these verification checks regularly.
diff --git a/guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc b/guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-and-backup-and-restore.adoc
@@ -46,5 +46,5 @@ Consider how many backups you want to store: Regularly removing outdated backups
 To make sure the active server is inaccessible, you can turn the machine off, halt the virtual machine (VM) if your server runs on a VM, or isolate the machine by using a firewall.
 .. Switch DNS records of the active server with the DNS records of the passive server.
 .. Assess the functionality of the test {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
 .. Perform these verification checks regularly.
diff --git a/guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-with-external-storage.adoc b/guides/common/modules/proc_preparing-for-disaster-recovery-with-active-and-passive-project-server-with-external-storage.adoc
@@ -37,7 +37,7 @@ To make sure the active server is inaccessible, you can turn the machine off, ha
 . Switch DNS records of the active server with the DNS records of the passive server.
 . Verify that your passive server can access the data stored on your shared storage.
 . Assess the functionality of the test {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
 . Perform these verification checks regularly.
 
 ifdef::satellite[]
diff --git a/guides/common/modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc b/guides/common/modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc
@@ -20,4 +20,4 @@ This redirects traffic from the old server to the new server and you will not ne
 
 .Verification
 * Assess the functionality of your restored {ProjectServer}.
-See xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
diff --git a/guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-and-backup-and-restore.adoc b/guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-and-backup-and-restore.adoc
@@ -10,4 +10,4 @@ If your active {ProjectServer} fails, activate your passive secondary server.
 . Switch DNS records of the active server with the DNS records of the passive server.
 This ensures that hosts remain connected and you do not need to re-register them.
 . Assess the functionality of your new active {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
diff --git a/guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-with-external-storage.adoc b/guides/common/modules/proc_recovering-from-disaster-with-active-and-passive-project-server-with-external-storage.adoc
@@ -14,4 +14,4 @@ This ensures that hosts remain connected and you do not need to re-register them
 . If your shared storage was mounted on both your active and passive servers, your passive server can already access the data.
 . If your shared storage was mounted only on your active server, re-mount it on your passive server.
 . Assess the functionality of your new active {ProjectServer}.
-For more information, see xref:Retrieving_the_Status_of_Services_{context}[].
+For more information, see xref:retrieving-the-status-of-services-by-using-cli_{context}[].
diff --git a/guides/common/modules/proc_retrieving-status-of-services-by-using-cli.adoc b/guides/common/modules/proc_retrieving-status-of-services-by-using-cli.adoc
@@ -1,18 +1,13 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="Retrieving_the_Status_of_Services_{context}"]
-= Retrieving the status of services
+[id="retrieving-the-status-of-services-by-using-cli_{context}"]
+= Retrieving the status of services by using Hammer CLI
 
+[role="_abstract"]
 {Project} uses a set of back-end services.
-When troubleshooting, you can check the status of {Project} services.
+When troubleshooting, you can check the status of {Project} services by using Hammer CLI.
 
 .Procedure
-* In the {ProjectWebUI}, navigate to *Administer* > *About*.
-** On the *Smart Proxies* tab, view the status of all {SmartProxies}.
-** On the *Compute Resources* tab, view the status of attached compute resource providers.
-** In the *Backend System Status* table, view the status of all back-end services.
-
-.CLI procedure
 * Get information from the database and {Project} services:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]

Original file line number	Diff line number	Diff line change
`@@ -8,4 +8,4 @@ include::modules/proc_preparing-for-disaster-recovery-by-virtualizing-your-proje`
`8`	`8`
`9`	`9`	`include::modules/proc_recovering-from-disaster-by-restoring-a-vm-snapshot-of-projectserver.adoc[leveloffset=+1]`
`10`	`10`
`11`		`-include::modules/proc_retrieving-status-of-services.adoc[leveloffset=+1]`
	`11`	`+include::modules/proc_retrieving-status-of-services-by-using-cli.adoc[leveloffset=+1]`