-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Uptime][Synthetics Integration] add browser callout #108935
[Uptime][Synthetics Integration] add browser callout #108935
Conversation
Pinging @elastic/uptime (Team:uptime) |
} | ||
values={{ | ||
link: ( | ||
<EuiLink target="_blank" href="" external> |
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 link still needs to be provided.
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.
For now I'd say https://www.elastic.co/guide/en/observability/current/synthetic-monitoring.html
is fine. I've opened elastic/observability-docs#989 to track adding more docs
@elasticmachine merge upstream |
@elasticmachine merge upstream |
To create a "Browser" monitor, please ensure you are using the "complete" elastic-agent Docker container as this contains the dependencies to run these monitors which can be downloaded from HERE. For more information, please visit our synthetics documentation. "here" links directly to the complete agent download instructions |
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.
Had a question about copy, otherwise looking good.
title={ | ||
<FormattedMessage | ||
id="xpack.uptime.createPackagePolicy.stepConfigure.monitorIntegrationSettingsSection.monitorType.browser.warning.description" | ||
defaultMessage='Browser monitoring requires using the "complete" variant of the elastic–agent docker container. Other distributions of elastic that agent will not work correctly with it because they lack the required browser and other binaries. For more information see our {link}' |
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.
defaultMessage='Browser monitoring requires using the "complete" variant of the elastic–agent docker container. Other distributions of elastic that agent will not work correctly with it because they lack the required browser and other binaries. For more information see our {link}' | |
defaultMessage='Browser monitoring requires using the "complete" variant of the elastic–agent docker container. Other distributions of elastic that agent will not work correctly with it because they lack the required browser and other binaries. For more information see our {link}.' |
Also, this sentence:
Other distributions of elastic that agent will not work correctly with it because they lack the required browser and other binaries.
This reads weirdly to me. Are we saying that "distributions of elastic" might not work correctly?
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 copy was a placeholder. Drew just provided the final version.
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.
Whoops, sorry, I saw that he commented and was confused why they didn't match. Should've put 2 + 2 together!
@elasticmachine merge upstream |
@@ -122,6 +124,34 @@ export const CustomFields = memo<Props>( | |||
/> | |||
</EuiFormRow> | |||
)} | |||
<EuiSpacer size="s" /> | |||
{isBrowser && ( |
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.
does it make sense to show this everytime user is adding a browser moniotor, is there a way to detect if they already have a working browser monitor, in that case i think user is probaly already educated and doesn;t need this additional context.
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.
That makes sense. There isn't a way to do this easily. We'd have to make a call to a fleet api to collect the users policies and check from there. Alternatively, we could do a query against the datastream to see if it has any documents with monitor.type
of browser.
It may be worth it to keep the call out though, since the user still need to make sure they are assigning the integration policy to the correct agent policy and they make have to change the selection at the bottom. Could be a good reminder.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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 !!
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
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
The following labels were identified as gaps in your version labels and will be added automatically:
If any of these should not be on your pull request, please manually remove them. |
Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: shahzad31 <[email protected]>
Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: shahzad31 <[email protected]>
Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: shahzad31 <[email protected]> Co-authored-by: Dominique Clarke <[email protected]> Co-authored-by: shahzad31 <[email protected]>
Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: shahzad31 <[email protected]> Co-authored-by: Dominique Clarke <[email protected]> Co-authored-by: shahzad31 <[email protected]>
Summary
Fixes #108710
Adds an EuiCallout when the browser option is selected.
The current content is under review. The content was pulled directly from the issue, but will be update upon product and design review.