-
Notifications
You must be signed in to change notification settings - Fork 32
Closed
Labels
Description
Describe the bug
Using the markdown below causes the Note two also add the heading and paragraph after it.
* Run {{agent}}'s status command:
* `sudo /opt/Elastic/Agent/elastic-agent status` (Linux)
* `sudo /Library/Elastic/Agent/elastic-agent status` (macOS)
* `c:\Program Files\Elastic\Agent\elastic-agent.exe status` (Windows)
If the status result for `endpoint-security` says that Endpoint has missed check-ins or `localhost:6788` cannot be bound to, it might indicate this problem is occurring.
* If the problem starts happening right after installing Endpoint, check the value of `fleet.agent.id` in the following file:
* `/opt/Elastic/Endpoint/elastic-endpoint.yaml` (Linux)
* `/Library/Elastic/Endpoint/elastic-endpoint.yaml` (macOS)
* `c:\Program Files\Elastic\Endpoint\elastic-endpoint.yaml` (Windows)
If the value of `fleet.agent.id` is `00000000-0000-0000-0000-000000000000`, this indicates this problem is occurring.
:::{note}
If this problem starts happening after Endpoint has already been installed and working properly, then this value will have changed even though the problem is happening.
:::
### Examine Endpoint logs [_examine_endpoint_logs]
If you’ve confirmed that the issue is happening, you can look at Endpoint log messages to identify the cause:
Expected behavior
The Note admonition should work within a list
Steps to reproduce
No response
Tooling
- docs-builder
- migration tooling
- I'm not sure