[Synthetics] add migration to supported monitor schedules and remove deprecated zip url fields

[dominiqueclarke]

Summary

Relates to #142655
Resolves #142653

Release notes

All monitor schedules in Uptime Monitor Management/Synthetics app apart from the supported schedules have been deprecated.

The only allowed schedules are the below:

Any monitor create in Uptime Monitor Management or Synthetics app using a schedule outside of the defined schedules in the screenshot have been moved to the nearest supported schedule.

Description

Adds a migration to transform unsupported schedules from Uptime Monitor Management to supported Synthetics app schedules. Also adds validation when an invalid schedule is used.

Also removes zip url fields from monitors. These fields were originally included in the saved object spec anticipating a future zip url feature. That feature has now been replaced by project monitors, removing the need for zip url fields.

Testing

⚠️ Note ⚠️

It's suggested that you use a fresh instance of ES to test this PR. This can either be done by creating a brand new oblt cluster via oblt-cli, or by running yarn es snapshot. If you run this PR on an existing oblt-cluster, then switch back to main on that same cluster before this PR is broken, you'll break the cluster.

Instructions

1. Check out 8.7.0
2. Create Uptime monitors with invalid schedules. Ideally, create one of each monitor type. Some example invalid schedules are 4, 8, 11, and 16, for example.
3. Create at least one of each type of project monitor by pushing monitors via the synthetics agent
4. Check out this branch
5. Navigate to Synthetics or Uptime once Kibana is done loading. Observe that each one of the invalid schedules was transformed into a supported schedule.
6. (Testing that decryption is still working after migration). Navigate to each one of the UI monitors' edit pages. Click save to resave each monitor. Then, visit the edit page again. If you don't see any page level errors, decryption is still working successfully
7. (Testing that decryption is still working after migration for project monitors). Change the global schedule your project monitors and repush. Check the global schedule of your project monitors one more time and repush again. If both pushes are successful, decryption is still working after the migration.

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[dominiqueclarke]

@shahzad31 For the throttling feature, any keys you want to remove from the saved object you'll want to make sure you include in this enum. This will ensure that the old legacy fields are excluded from AAD when migrated, and ensure that decryption is able to progress with the legacy fields missing.

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[dominiqueclarke]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 729cade

Failed CI Steps

• FTR Configs #29

Test Failures

• [job] [logs] FTR Configs #29 / logstash pipelines delete "before all" hook: load pipelines archive for "should delete the specified pipelines"

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
synthetics	1.4MB	1.4MB	-1.7KB

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	432	435	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	512	515	+3

History

• 💔 Build #117729 failed 332d50b
• 💔 Build #117714 failed 8370321
• 💔 Build #117266 failed 03c33ed
• 💔 Build #117265 failed c68be93
• 💔 Build #117262 failed db8dca1

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[shahzad31]

LGTM. Works as expected !!