org.llm4s.spring

Sizing of the executor behind LLM4STemplate's completeAsync (llm4s.async.*).

Health indicator settings (llm4s.health.*).

What the indicator reports about and how it probes; the secrets are only used to redact messages.

Spring-friendly entry point to an LLM.

complete and tryComplete block the calling thread. completeAsync never does: the blocking call runs on executor (the llm4sTaskExecutor bean) and the returned future completes from there. Cancelling the future with cancel(true) interrupts the provider call, which is how llm4s cancels work; a failure completes the future exceptionally with the LlmException.

Name of the executor bean behind completeAsync and the health probe; define a bean of this name to replace it.

Reports what was actually checked. By default (llm4s.health.probe=false) it makes no provider call: it is UP with probe=disabled and the provider and model names, meaning "configured", not "reachable". With llm4s.health.probe=true it sends a one-token completion on executor, waits at most llm4s.health.probe-timeout, and caches the outcome for llm4s.health.probe-ttl. A failed or timed-out probe is DOWN with a redacted message.

health() never throws InterruptedException: a thread interrupted while it waits for the probe gets DOWN with probe=cancelled, its interrupt flag set again, and the probe call is cancelled. That outcome is not cached: it is about the interrupted thread, not the provider, so the next check probes again.

Records llm4s request, token, cost and error metrics in the application's Micrometer MeterRegistry, so they appear on /actuator/metrics (and in whatever the registry exports to) with no wiring.

Active when llm4s-observability-micrometer is on the classpath and the context has a MeterRegistry bean, as Spring Boot Actuator provides. The starter declares that module provided, like Actuator itself, so an application opts in by adding the dependency. A MetricsCollector bean of the application's own replaces this one; the client bean reports to every MetricsCollector bean there is.

It runs after the auto-configurations that create the MeterRegistry, so @ConditionalOnBean sees it. They are named as strings, because Actuator is optional, and Spring Boot 4 moved them from org.springframework.boot.actuate.autoconfigure.metrics (spring-boot-actuator-autoconfigure) to org.springframework.boot.micrometer.metrics.autoconfigure (spring-boot-micrometer-metrics), so both names are listed; Spring ignores a name that is not on the classpath. LlmMetricsAutoConfigurationOrderingSpec fails if a Boot 3 name stops resolving on the Boot version the starter is tested against, or if the Boot 4 names are dropped.