-
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] Update notices and banners from experimental to beta #91421
Comments
Pinging @elastic/uptime (Team:uptime) |
cc @elastic/observability-design / @drewpost |
@paulb-elastic
|
@drewpost we are getting closer to needing to make this change for beta - can you provide the copy and link please? |
Text for the warning on Monitor Details page. I want to keep it short and sweet. Beta See More (link to https://www.elastic.co/what-is/synthetic-monitoring ) |
Thanks @drewpost |
@drewpost @paulb-elastic What was the determination made for the Elastic Synthetics callout? I know we discussed it in a past meeting, but it doesn't appear as if the decision was documented. |
Confirmed with @drewpost in refinement that we will keep the main Synthetics call out implementation. |
At least until we get to GA. It's also experiment/beta/ga agnostic text so it won't require any further updating. Additionally, if a user has surpassed the message before, they will not be shown the message again after updating. |
During the change of phase from Experimental to Beta, we need to update some of the working and signposting that currently exists.
At the moment, there is a callout to Synthetics when you go into Uptime (although it does not specifically mention experimental, or beta). This includes a Read announcement link to https://www.elastic.co/what-is/synthetic-monitoring

This can be dismissed so it does not keep appearing.
There is also a callout, to Experimental... when expanding a test result on the History page:

This does not have a dismiss option, or a link to find out more details.
During a recent discussion, it was suggested this might be better to be shown against the monitor (further up the page, rather than against a specific test results), as well as to include a link out to find out more details.
This issue needs some input from @elastic/observability-design and @drewpost to define:
The text was updated successfully, but these errors were encountered: