Skip to content

The spring-integration actuator endpoint doesn't work when multiple MeterRegistry beans are registered #9335

Closed
@trask

Description

@trask

Expected Behavior

The spring-integration actuator endpoint should still work when multiple MeterRegistry beans have been registered (which is a use case that the regular spring metrics actuator endpoint supports).

Current Behavior

The spring-integration actuator endpoint doesn't work when multiple MeterMeterRegistry beans have been regsitered, see

Map<String, MeterRegistry> registries = applicationContext.getBeansOfType(MeterRegistry.class, false, false);
if (registries.size() == 1) {
this.registry = registries.values().iterator().next();
}
else {
this.registry = null;
}

Context

The regular spring metrics actuator endpoint supports multiple MeterRegistry beans, and it would be great if the spring-integration actuator endpoint had similar support, see

I have not found any workaround to make the spring-integration actuator endpoint work when multiple MeterRegistry beans have been registered.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions