Skip to content

fix(logging): monitor configured service reachability#2360

Open
kkovaacs wants to merge 1 commit into
krisztian/log-startup-shutdown-eventsfrom
krisztian/log-service-availability-events
Open

fix(logging): monitor configured service reachability#2360
kkovaacs wants to merge 1 commit into
krisztian/log-startup-shutdown-eventsfrom
krisztian/log-service-availability-events

Conversation

@kkovaacs

Copy link
Copy Markdown
Contributor

Summary

  • Add non-blocking reachability monitors for configured validator, sequencer, NTX builder, and remote prover endpoints.
  • Warn on the first failed connection attempt, retry with capped exponential backoff, and log when the service becomes reachable.
  • Sanitize endpoint URLs before logging them.
  • Stop monitors cleanly during shutdown.

Partially resolves point 5 of #2330

Changelog

[[entry]]
scope       = "general"
impact      = "added"
description = "User-visible warnings for unreachable external service endpoints have been added, making potential mis-configuration easier to spot."

block_prover_monitor
.monitor::<RemoteProverClient>("block-prover", shutdown.clone()),
);
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this monitoring not be inherent in the connections that the sequencer has to the various components? Why is a separate monitor required?

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.

2 participants