[Uptime][Synthetics integration] remove optional tag from timeout field

[dominiqueclarke]

Summary

Fixes #99373

Removes Optional tag from timeout field

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[justinkambic]

Now that I'm seeing this I'm wondering if it should be Optional after all. You can omit the timeout field from a Heartbeat YAML file and it will just use its default 16s. cc @andrewvc any thoughts?

[dominiqueclarke]

@justinkambic @andrewvc I'm handling some of the defaults by matching what is defaulted in heartbeat to the default value that is populated in the fields on mount. Since the default timeout is 16 seconds, I use 16 seconds as the default value. I think it would be confusing, in some ways, if a user omitted this entirely and yet the timeout applied was still the default 16 seconds. I think current UX better aids in ensuring the policy that is created is the policy the user intended.

[dominiqueclarke]

@elasticmachine merge upstream

[dominiqueclarke]

@elasticmachine merge upstream

[justinkambic]

it would be confusing, in some ways, if a user omitted this entirely and yet the timeout applied was still the default 16 seconds. I think current UX better aids in ensuring the policy that is created is the policy the user intended.

That's a good point. Ok, I'm fine with it being required, esp. since we give the default value HB will use anyway.

We also discussed offline the implications of requiring the timeout to be lower than the interval. When configuring HB manually, it will allow the interval to be below the timeout.

We feel that since this is not a frequent configuration choice, and that it's probably not a good practice anyway, we will leave in the requirement that the request timeout be faster than the ping interval.

[justinkambic]

LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 02e576c
• Storybooks Preview

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
uptime	1.2MB	1.2MB	-85.0B

Unknown metric groups

References to deprecated APIs

id	before	after	diff
canvas	29	25	-4
crossClusterReplication	8	6	-2
fleet	4	2	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	5	3	-2
licensing	18	15	-3
monitoring	109	56	-53
total			-73

History

• 💚 Build #125007 succeeded e99b60d
• 💚 Build #124577 succeeded 080efd4

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

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.13
✅	7.x

The backport PRs will be merged automatically after passing CI.