-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Heartbeat] Support PlaywrightOptions #28197
Comments
Pinging @elastic/uptime (Team:Uptime) |
Discussed in refinement (elastic/synthetics#388 (comment)) and the initial focus will be on Playwright options (which themselves can be used for defining proxy settings). Future enhancements can be made to specifically call out configurations like proxy settings. Description/ACs updated accordingly. |
This has to go in 8.3 because we are doing PUSH command and it would be weird not to have on the HB side since Synthetics and Kibana already support this option. |
Fixes elastic#28197 Adds the new `playwright_options` browser option. Test with the following config manually: ```yaml - type: browser enabled: true id: browser-inline name: browser-inline ignoreHTTPSErrors: true throttling: download: 1.6 upload: 0.75 latency: 150 source: inline: script: step("load homepage", async () => { await page.goto('https://www.elastic.co'); }); step("hover over products menu", async () => { await page.hover('css=[data-nav-item=products]'); }); step("failme", async () => { await page.hhover('css=[data-nav-item=products]'); }); schedule: "@every 1m" ```
Fixes #28197 Adds the new `playwright_options` browser option. Test with the following config manually: ```yaml - type: browser enabled: true id: browser-inline name: browser-inline ignoreHTTPSErrors: true throttling: download: 1.6 upload: 0.75 latency: 150 source: inline: script: step("load homepage", async () => { await page.goto('https://www.elastic.co'); }); step("hover over products menu", async () => { await page.hover('css=[data-nav-item=products]'); }); step("failme", async () => { await page.hhover('css=[data-nav-item=products]'); }); schedule: "@every 1m" ```
Post-FF testing LGTM I tested this by configuring an inline monitor like: - type: browser
enabled: true
id: synthetic-inline-tests
name: Elastic website
schedule: '@every 10s'
playwright_options:
headless: false
source:
inline:
script: |-
step("load homepage", async () => {
await page.goto('https://www.elastic.co');
}); The test was to pass the |
Fixes #28197 Adds the new `playwright_options` browser option. Test with the following config manually: ```yaml - type: browser enabled: true id: browser-inline name: browser-inline ignoreHTTPSErrors: true throttling: download: 1.6 upload: 0.75 latency: 150 source: inline: script: step("load homepage", async () => { await page.goto('https://www.elastic.co'); }); step("hover over products menu", async () => { await page.hover('css=[data-nav-item=products]'); }); step("failme", async () => { await page.hhover('css=[data-nav-item=products]'); }); schedule: "@every 1m" ```
Heartbeat counterpart to elastic/synthetics#388, proposes support for a new option for browser monitors
ACs:
playwright_options
parameter that defined the JSON to be passed to playwright directly (as added to Synthetics in Support Playwright options (e.g. to define HTTP proxies) synthetics#388)The text was updated successfully, but these errors were encountered: