Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observer list and status #27

Open
ch1bo opened this issue Feb 11, 2025 · 1 comment
Open

Observer list and status #27

ch1bo opened this issue Feb 11, 2025 · 1 comment

Comments

@ch1bo
Copy link
Member

ch1bo commented Feb 11, 2025

Why

The explorer has multiple observers scanning the chain (on multiple networks). The user interface or API, however, does not provide any observability of that process. For example it is not clear which observers are currently online or whether the observer has already reached the tip or not.

Image

What (TBD)

  • Add an API endpoint that lists known /observers that contains information about the last processed block/slot of each observer
  • Visualize in the last seen tick of an observer vs. other observers?
@ch1bo
Copy link
Member Author

ch1bo commented Feb 12, 2025

Related to this is also that the logs available on the explorer container are not indicating whether a head transaction was observed or only a new block (tick):

Image

So maybe splitting the observer API into two routes could help in observability too?

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

No branches or pull requests

1 participant