Skip to content

Add option to prune obsolete INFO_UPDATED events on append - #5664

Merged
andreasfritz merged 1 commit into
codecentric:masterfrom
PineeAppleee:feature/5605-prune-info-updated-events
Sep 18, 2026
Merged

andreasfritz merged 1 commit into
codecentric:masterfrom
PineeAppleee:feature/5605-prune-info-updated-events

Conversation

@PineeAppleee

Copy link
Copy Markdown
Contributor

Closes #5605

What this does

Adds a new opt-in configuration property
spring.boot.admin.event-store.prune-info-updated-events that, when
enabled, keeps only the latest INFO_UPDATED event per instance
instead of retaining all of them in memory until the normal
size-based compaction runs.

Default is false, so existing behavior is unchanged unless
explicitly opted in.

Changes

  • AdminServerProperties: new EventStoreProperties.pruneInfoUpdatedEvents property
  • ConcurrentMapEventStore: new constructor overload + pruning logic in doAppend()
  • InMemoryEventStore: new constructor overload accepting the flag
  • AdminServerAutoConfiguration: wires the property into the eventStore bean

Testing

Added two tests in InMemoryEventStoreTest covering both the
enabled and disabled cases. Full test suite passes (483 tests,
0 failures).

Adds a new opt-in configuration property
spring.boot.admin.event-store.prune-info-updated-events that, when
enabled, keeps only the latest INFO_UPDATED event per instance
instead of retaining all of them until compaction.

Closes codecentric#5605
@PineeAppleee
PineeAppleee requested a review from a team as a code owner September 14, 2026 20:48
@andreasfritz
andreasfritz merged commit 21bdc88 into codecentric:master Sep 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: Allow to keep only the latest INFO_UPDATED event

2 participants