Open
Conversation
5c56d74 to
ac15232
Compare
Collaborator
|
@SantiagoPittella I think it makes sense to add those - I imagine to the node's compose file that @sergerad is adding. There should be an open issue about adding more stuff to the compose file. |
sergerad
reviewed
Apr 9, 2026
sergerad
reviewed
Apr 9, 2026
sergerad
approved these changes
Apr 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #1888
Simplifies NTX actor startup by removing the
AccountOriginenum. Actors now take a plainNetworkAccountIdand on startup wait for a committed account state in the database before producing transactions.The coordinator can now blindly spawn actors without caring about where the account state comes from since the actor handles it internally.
Regarding monitoring
cc @sergerad @Mirko-von-Leipzig
Additionally, and did not commit it, to monitor the actgor's spawning I added a local observability setup using Grafana and Tempo, using the already exported traces from the node.
This adds a
docker-compose.ymlthat spins up Tempo as the trace backend and Grafana as the dashboard frontend. Tempo receives traces on port 4317 and Grafana is pre-configured with Tempo as a datasource so there is zero manual setup.This is useful for debugging NTX actor behavior during development since you can see the full span tree for actor spawns, transaction execution, block commits, and gRPC calls; and also Tempo can derive rate, error rate, and duration metrics from traces, which was really useful to track actors spawning.
I can create a PR with that setup if you guys consider it worth it.