The fleet-server currently does no additional validation for config values, anything that is parsable by go is passed to fleet. This may result in values such as a negative duration being accepted and passed down.
For example durations (for cache config) can be set to negative numbers in Kibana (also jitter in this example is greater then any TTL):
The fleet-server currently does no additional validation for config values, anything that is parsable by go is passed to fleet. This may result in values such as a negative duration being accepted and passed down.
For example durations (for cache config) can be set to negative numbers in Kibana (also jitter in this example is greater then any TTL):
Leading to the following config running on an elastic-agent running fleet-server:
And the fleet-server logs have no issues accepting these values (negative numbers, jitter > TTL):
cc: @scunningham