-
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
Add documentation clarification #3382
Add documentation clarification #3382
Conversation
A documentation preview will be available soon: |
This pull request does not have a backport label. Could you fix it @paulb-elastic? 🙏
|
@elasticmachine run elasticsearch-ci/docs |
@elasticmachine run elasticsearch-ci/docs |
@@ -77,6 +77,11 @@ Read more in <<synthetics-params-secrets>>. | |||
|
|||
For all available options, refer to the https://playwright.dev/docs/test-configuration[Playwright documentation]. | |||
|
|||
[NOTE] | |||
==== | |||
Synthetics will always run browser monitors in headless mode (it is not possible to configure them to run in headful mode, even if setting Playwright options). |
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.
I would have said "even forcing headless:false
via Playwright options, we do not support running browser monitors in headful mode".
Maybe, can share an hint of passing a user agent like here if really needed? https://github.com/elastic/synthetics/blob/d33d899bafa686da0b547afd2145db51b411ed1b/examples/todos/synthetics.config.ts#L12
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.
@lucabelluccini I thought the confusion was originally because someone was specifically trying to run in headful mode - were they doing this because they wanted a non headless UA string then?
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.
I do not have the whole detail about it, we can check together in Slack
@@ -167,6 +167,11 @@ Use Playwright to simulate and validate user workflows including: | |||
|
|||
Visit the https://playwright.dev/docs[Playwright documentation] for information. | |||
|
|||
[NOTE] |
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.
This is a bit confusing for me, I've used headful mode for debugging on synthetics cli, shouldn't this specifically refer to Elastic hosted synthetics service/heartbeat monitors instead?
Running headful locally used to be supported. IMO, it should still be
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.
@emilioalvap that's correct, it is still possible via the CLI, which is why I didn't add the note there
I also specifically mentioned ...run browser monitors...
to try and distinguish this as the monitor (not running the journey locally for debugging purposes), but it sounds like this was still confusing. I didn't want to add a link here to the CLI saying it was still possible, as I thought it would get too confusing, but do you think that would help then?
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.
I think the wording on the CLI specific page is quite detailed, I'd replicate that here:
Do not attempt to run in headful mode when running through Elastic’s global managed testing infrastructure or Private Locations as this is not supported.
IMO, this page is more generic than the CLI one to simply state that headful mode is not supported, it might be confusing for users as well.
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.
LGTM
@elasticmachine, run elasticsearch-ci/docs |
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.
Some questions and suggestions below.
* *A full URL using the syntax `scheme://<host>:[port]`*, where: | ||
** `scheme` is one of `tcp`, `plain`, `ssl` or `tls`. If `tcp` or `plain` is specified, Synthetics establishes a TCP connection even if the monitor is configured to use SSL. If `tls` or `ssl` is specified, Synthetics establishes an SSL connection. However, if the monitor is not configured to use SSL, the system defaults are used (currently not supported on Windows). | ||
** `host` is the hostname. | ||
** `port` is the port number. If `port` is missing in the URL, the <<monitor-tcp-ports,`ports`>> setting is required. | ||
** `port` is the port number. |
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.
@paulb-elastic this is the change I pushed to get the build to succeed (this line was still linking to the ports
option, which was removed below). Should the whole line be removed instead?
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.
Ah, thanks @colleenmcginnis!!
I think this part of line 18 should still be there as it describes what the port
is under the A full URL using the syntax section
[source,yaml] | ||
---- | ||
hosts: ["localhost:8000"] | ||
hosts: "localhost" |
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.
I noticed you removed "A plain host name, such as localhost
, or an IP address." above. Should we also remove this example?
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.
Thanks - good catch, removing
* *A plain host name, such as `localhost`, or an IP address.* | ||
If you specify this option, you must also specify a value for <<monitor-tcp-ports,`ports`>>. If the monitor is {heartbeat-ref}/configuration-ssl.html[configured to use SSL], Synthetics establishes an SSL/TLS-based connection. Otherwise, it establishes a plain TCP connection. | ||
(<<synthetics-lightweight-data-string,string>>) | ||
a| *Required*. The host to ping. The entries in the list can be: |
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.
a| *Required*. The host to ping. The entries in the list can be: | |
a| *Required*. The host to ping. The value can be: |
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.
Good catch, thanks
Thanks for the feedback @colleenmcginnis, updated as per the comments |
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.
✨
💚 Build Succeeded
History
|
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331) # Conflicts: # docs/en/observability/synthetics-configuration.asciidoc
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331)
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331)
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331)
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331) Co-authored-by: Paul Bianciardi <[email protected]>
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331) Co-authored-by: Paul Bianciardi <[email protected]>
* Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331) Co-authored-by: Paul Bianciardi <[email protected]>
…#3384) * Add documentation clarification (elastic#3382) * Update how hosts and ports are configured * Add that monitors cannot be run headful (cherry picked from commit 3271331) # Conflicts: # docs/en/observability/synthetics-configuration.asciidoc * fix conflicts --------- Co-authored-by: Paul Bianciardi <[email protected]> Co-authored-by: Colleen McGinnis <[email protected]>
Following on from #3263, there are more places where this limitation was not reflected in the documentation. This is also true for not supporting
ports
in Project Monitors.The docs have also been updated to clarify that monitors cannot run in headful mode, but always headless, and cannot be overridden with Playwright Options.