Differences from Spring

The actuator follows Spring Boot Actuator: the same paths, properties, media types and JSON. This page lists where it does not, and why.

Why

The actuator is young: its first part covers what load balancers, Kubernetes and operators ask most (health, info, mappings). Other differences come from Dart: no JMX, no servlet container, no java runtime to describe.

Example

The same configuration in both:

management.endpoints.web.exposure.include=health,info
management.endpoint.health.show-details=when-authorized
management.endpoint.health.probes.enabled=true

The differences

Spring Boot Here Why
About twenty endpoints (beans, env, conditions, loggers, metrics, startup, logfile...) health, info and mappings; the others come later. Three of its own: jsonschemas, isolates and qps First part
Read, write and delete operations Read operations only
HTTP and JMX HTTP only No JMX in Dart
management.server.port for a separate port The main server only, so an additional path is only server:; no management CORS settings Not implemented yet
HealthIndicator and ReactiveHealthIndicator One HealthIndicator, whose health() may return a Future Dart's Future
An indicator that throws fails the request It is DOWN with the error as detail
A part of a group found by path even when it is not a member Found through the group only when it is a member
HealthComponent, CompositeHealth, SystemHealth (Spring Boot 3) Spring Boot 4's names: HealthDescriptor, CompositeHealthDescriptor, SystemHealthDescriptor
Disk space from Java's File df (Linux, macOS) or .NET's DriveInfo (Windows); UNKNOWN where neither exists (iOS, the web) No disk API in dart:io
java, process, ssl info contributors dart instead of java; no process or ssl; the os values are Dart's
classpath:META-INF/build-info.properties, written by the Maven or Gradle plugin resources:build-info.properties, written by the generator for applications (name and version, no time) No build plugin
classpath:git.properties, written by a plugin resources:git.properties, written by you or CI
mappings in Spring MVC's or WebFlux's shape WebFlux's shape (dispatcherHandlers); the descriptor is the Dart signature; screens added by the navigation starter The web starter is not a servlet container
management.endpoint.<id>.enabled (Boot 2 and 3) or .access (Boot 3.4+) Both read; access wins Configurations of both generations work
EndpointRequest matches path patterns It matches the requests the actuator's web layer recorded (a request attribute) Follows the base path and mappings exactly

See also