Skip to content

Commit bac664a

Browse files
Fixes attribute syntax in Troubleshoot Elastic Defend
1 parent 7893306 commit bac664a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

troubleshoot/security/elastic-defend.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ To restart a transform that’s not running:
102102
:::::
103103

104104

105-
:::::{dropdown} {agent} and Endpoint connection issues
105+
:::::{dropdown} {{agent}} and Endpoint connection issues
106106
:name: ts-agent-connection
107107

108108
After {{agent}} installs Endpoint, Endpoint connects to {{agent}} over a local relay connection to report its health status and receive policy updates and response action requests. If that connection cannot be established, the {{elastic-defend}} integration will cause {{agent}} to be in an `Unhealthy` status, and Endpoint won’t operate properly.
@@ -168,7 +168,7 @@ To debug and resolve the issue, follow these steps:
168168
:::::
169169

170170

171-
::::{dropdown} {elastic-defend} deployment issues
171+
::::{dropdown} {{elastic-defend}} deployment issues
172172
:name: defend-deployment
173173

174174
After deploying {{elastic-defend}}, you might encounter warnings or errors in the endpoint’s **Policy status** in {{fleet}} if your mobile device management (MDM) is misconfigured or certain permissions for {{elastic-endpoint}} aren’t granted. The following sections explain issues that can cause warnings or failures in the endpoint’s policy status.

0 commit comments

Comments
 (0)