-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update synthetics-private-location.asciidoc #4234
Conversation
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this.
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. You could also consider using bold text in the paragraph above:
Elastic provides Docker images that you can use to run Fleet and an Elastic Agent more easily. For monitors running on Private Locations, you must use the
elastic-agent-complete
Docker image to create a self-hosted Elastic Agent node. The standard Elastic Cloud or self-hosted Elastic Agent will not work.
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this. (cherry picked from commit 97e4252)
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this. (cherry picked from commit 97e4252)
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this. (cherry picked from commit 97e4252) Co-authored-by: Jan Doberstein <[email protected]>
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this. (cherry picked from commit 97e4252) Co-authored-by: Jan Doberstein <[email protected]>
As we have had multiple support cases where customers tried to run browser-based checks via different installation procedures and even support engineers struggled to see the note above my change, I think this is important to reduce the number of cases with this.