Bug: StatusUpdater timeout is ignored

[cdprete]

Spring Boot Admin Server information

• Version: 4.0.2

• Spring Boot version: 4.0.3

• Configured Security: None

• Webflux or Servlet application: WebFlux

Client information

Not needed.

Description

Hello.

According to the documentation at https://docs.spring-boot-admin.com/4.0.2/docs/customization/monitoring/custom-health-status/#example-custom-timeout, it should be possible to change the timeout used by the StatusUpdater by simply defining the bean in the context with the wanted timeout.

Too bad that StatusUpdateTrigger changes it to the value interval from IntervalCheck, ignoring therefore the value set previously:

[cdprete]

I can confirm it's ignored since I've set it to 30s but then I can still see status events like

{
  "data": {
    "instance": "c19d849cce89",
    "version": 1415,
    "type": "STATUS_CHANGED",
    "timestamp": "2026-03-12T14:17:50.594Z",
    "statusInfo": {
      "status": "OFFLINE",
      "details": {
        "exception": "java.util.concurrent.TimeoutException",
        "message": "Did not observe any item or terminal signal within 9000ms in 'log' (and no fallback has been configured)"
      },
      "outOfService": false,
      "restricted": false
    },
    "key": "c19d849cce89-1415-STATUS_CHANGED-1773325070594",
    "date": "2026-03-12T14:17:50.594Z",
    "application": "BFP (INT)"
  },
  "index": 3
}

where 9s is reported instead of 29s.

[cdprete]

Hi @SteKoe.
Can we please add a configuration property (e.g.: statusTimeout) under https://github.com/codecentric/spring-boot-admin/blob/master/spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerProperties.java#L91 so that there is no need to redefine the bean in the context for it?

This is just a side request and I can easily open a PR for it.
Of course, it doesn't fix the issue reported in here.