Merge pull request #49323 from lahinson/etcd-auto-defrag

updating log output example messages

Author: opayne1

modules/etcd-defrag.adoc

@@ -34,14 +34,18 @@ Verify that the defragmentation process is successful by viewing one of these lo
 Automatic defragmentation can cause leader election failure in various OpenShift core components, such as the Kubernetes controller manager, which triggers a restart of the failing component. The restart is harmless and either triggers failover to the next running instance or the component resumes work again after the restart.
 ====
 
-.Example log output
+.Example log output for successful defragmentation
 [source,terminal]
+[subs="+quotes"]
 ----
-I0907 08:43:12.171919       1
-defragcontroller.go:198] etcd member "ip-
-10-0-191-150.example.redhat.com"
-backend store fragmented: 39.33 %, dbSize:
-349138944
+etcd member has been defragmented: __<member_name>__, memberID: __<member_id>__
+----
+
+.Example log output for unsuccessful defragmentation
+[source,terminal]
+[subs="+quotes"]
+----
+failed defrag on member: __<member_name>__, memberID: __<member_id>__: __<error_message>__
 ----
 
 [id="manual-defrag-etcd-data_{context}"]