[Synthetics] Notify legacy Synthetics integration being deprecated

[paulb-elastic]

As part of deprecating the Synthetics Integration in 8.8 (#137505) we need stronger messaging in 8.7 to make this clear to start moving monitors across.

ACs:

• If there are any Synthetics Integration monitors configured (browser Zip URL and/or Inline, or any leigthweight monitor types), add a notification banner to the top of Uptime
• In the edit flow of the existing Integration Policy, add a notification
• Add details to the main integration Overview
• The notification should be along the lines of (copy to be checked by @florent-leborgne)

  You have at least one Elastic Synthetics Integration monitor configured. These monitors will stop running and become inaccessible from 8.8. Please migrate them over to either Project Monitors (most useful for Zip URL Integration monitor types) or add them to the Synthetics App (most useful for Inline Synthetics Integration monitor types). See the docs for more information.

• Add details about the upcoming deprecation to the release note for 8.7

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[florent-leborgne]

Hi @paulb-elastic, here's an attempt on the wording for the banner:

---

Migrate your Elastic Synthetics integration monitors before Elastic 8.8

You have at least one monitor configured using the Elastic Synthetics integration.
 These monitors will stop running and become unavailable from Elastic 8.8. 
To avoid this, migrate them to Project monitors or add them to the new Synthetics app directly available in Observability before the 8.8 update.

Check our Synthetics migration docs for more details.

---

• The migration docs linked for now use the name "Uptime app", so just a note to align the names or remember to also replicate the name change from 8.7 in these docs, (or use Uptime here if the renaming doesn't happen).
• I've for now removed what you had suggested between brackets to shorten the message. I'd instead suggest to make these recommendations or tips clearer in the migration docs.
• I've not used the word "deprecated" anywhere yet. But we could put it in the title as well to make it even clearer.

Hope this helps, feel free to adjust or ask for more input :)

Edit 1: Updated after @shahzad31's comment below.
Edit 2: Reverted to "stop running" wording after confirmation from Paul

[shahzad31]

@florent-leborgne @paulb-elastic just to clarify one point

These monitors will stop running and become unavailable from Elastic 8.8. Monitors will not stop running. It's just that user will not be able to edit them. For monitors to stop running users will have to delete the integrations they have added.

[florent-leborgne]

Thanks for the additional context @shahzad31! I've updated the wording suggestion to take this into account. I'd recommend making it clear in the linked docs that removing the old integrations is part of the migration process users should follow.

[afgomez]

To confirm, this refers to all monitors created via the synthetics integration, not only the browser ones, correct?

[paulb-elastic]

Monitors stpping running

That was the requirement in #137505 but it seems it isn't possible

To confirm, this refers to all monitors created via the synthetics integration, not only the browser ones, correct?

@afgomez correct, any monitor configured via the Synthetics Integration will trigger the warning message (I have updated the description to clarify this, as it wasn't clear, thanks)

[afgomez]

Thank you @paulb-elastic!

I think it also makes sense to update the integration description itself, explaining that it is deprecated and monitors should be migrated

[paulb-elastic]

update the integration description itself

Good idea, I'l add to the description

[paulb-elastic]

@florent-leborgne @afgomez we've confirmed that monitors will stop running from 8.8 (albeit we will implement this in Beats now).

As such, please ensure the messaging makes it clear we will be stopping them running in the next version and they will be inaccessible.

(we won't auto delete them, but the UI won't be there to allow them to see the configuration, and they won't run anymore)

[florent-leborgne]

@paulb-elastic I've reverted some of the wording suggestion in my previous comment to reflect your update.
Hope this helps.

[paulb-elastic]

It seems the main Integration Overview doesn't have an updated banner yet (have asked @dominiqueclarke, this may need to be changed in the Integration rather than Kibana).

Also the docs link is going to ...synthetics-get-started-project.html#synthetic-monitor-choose-project instead of ...synthetics-migrate-from-integration.html, I've raised #150872 to cover this.

[paulb-elastic]

Created elastic/integrations#5258 for the last AC

[dominiqueclarke]

Post FF testing LGTM in 8.7.0-SNAPSHOT