From 01dba2a3b4b2e192b2f2f6dcae14c32261b7a02c Mon Sep 17 00:00:00 2001
From: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
Date: Tue, 23 Jan 2024 17:13:14 -0600
Subject: [PATCH] Update
 docs/en/observability/profiling-self-managed-troubleshooting.asciidoc

---
 .../profiling-self-managed-troubleshooting.asciidoc           | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/en/observability/profiling-self-managed-troubleshooting.asciidoc b/docs/en/observability/profiling-self-managed-troubleshooting.asciidoc
index 2a165cf17c..4cf2902517 100644
--- a/docs/en/observability/profiling-self-managed-troubleshooting.asciidoc
+++ b/docs/en/observability/profiling-self-managed-troubleshooting.asciidoc
@@ -88,5 +88,7 @@ In the case of collectors, the component responsible for ingesting data in Elast
 For symbolizers most of the logs will be related to the processing of native frames, initially detected by the collector.
 
 If you are troubleshooting startup issues for both services, logs are the most useful source of information.
-On startup, each service will log if it is able to parse configurations and to start serving the incoming requests.
+On startup, each service generates logs indicating whether it was able or unable to parse configurations and begin processing incoming requests. 
+Any startup errors will be logged using the `log.level=error` field.
+Use these error logs to find misconfigurations or other issues that could prevent the service from starting.
 Errors will be logged using the `log.level=error` field: they can be used to spot misconfigurations or other issues that prevent the service from starting up.