[APM] Warning in APM Integration Editor caused by invalid default duration

[sorenlouv]

Under the Advanced Options in the APM Integration Editor we display a warning "Must be greater than 1ms" for the option "Maximum duration for reading an entire request".

The warning is displayed because the value (3600) doesn't contain a unit ("ms").

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[cauemarcondes]

We should either fix the default value to send the unit alongside the value, or on the UI add a default value for the unit as suggested by @ogupte . @simitt wdyt?

[simitt]

The default value actually contains a unit, it is set to 3600s (https://github.com/elastic/apm-server/blob/master/apmpackage/apm/manifest.yml#L109-L111).
What might be happening here is that this value is sent via the APM Server configs when the server starts up.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[joshdover]

Test instructions:

• Launch 8.1.0 cluster on Cloud staging (I think you're going to need to wait for BC4)
• Switch to managed APM by going to APM/Settings/Schema/Switch to Elastic Agent
• Open the edit form on the APM integration policy on the Elastic Cloud agent policy
• Expand the "Advanced options" accordion (not the one below the integration name, the one further down the page)
• Verify that there is no validation warning on "Maximum duration for reading an entire request" and the value is set to 3600s

[amolnater-qasource]

Hi @joshdover
We have revalidated this issue on latest 8.1 BC-4 Kibana cloud environment and found it working fine.

• There is no validation warning on "Maximum duration for reading an entire request" and the value is set to 3600s.

Build details:
VERSION: 8.1.0
BUILD: 50428
COMMIT: 015578b

Screenshot:

Hence marking this as QA:Validated.
Thanks