feat(dashboard): add block transaction count and SR set change panels#118
Open
warku123 wants to merge 4 commits into
Open
feat(dashboard): add block transaction count and SR set change panels#118warku123 wants to merge 4 commits into
warku123 wants to merge 4 commits into
Conversation
Add two new panel sections to the java-tron-server Grafana dashboard to support metrics from tronprotocol/java-tron#6624: - Block Metrics: empty block rate, per-SR empty block count, avg transactions per block, transaction count distribution - SR Set Change: event table and cumulative totals by action
Add descriptions for the new metrics under "Blockchain status" and "Block status" sections so node operators can discover and use them.
167304e to
7096913
Compare
Sunny6889
reviewed
May 6, 2026
| - `tron:verify_sign_latency_seconds_count`: Count of events | ||
| - `tron:verify_sign_latency_seconds_sum`: Total sum of all observed values | ||
|
|
||
| Histogram of transaction count per block, with buckets `[0, 10, 50, 100, 200, 500, 1000, 2000, 5000, 10000]`. Empty blocks can be queried via the `le="0.0"` bucket; the distribution buckets enable transaction volume analysis (P50/P99, large-block ratio, etc.): |
Contributor
There was a problem hiding this comment.
Please change the default buckets to align with java-tron latest metrics
Author
There was a problem hiding this comment.
Done in ad334cb — bucket array updated to match the refined values in tronprotocol/java-tron#6730. Also note the dashboard panel was already realigned to the new boundaries in f9325c7 earlier in this PR.
The block_transaction_count histogram buckets in java-tron are being refined to [0, 20, 50, 80, 100, 120, 140, 160, 180, 200, 230, 260, 300, 500, 2000] (tronprotocol/java-tron#6730), densifying the 0-300 range for percentile interpolation in the typical per-SR TPS range. Update the Block Transaction Count Distribution panel to match: the old le="10.0" and le="1000.0" boundaries no longer exist in the refined array, so those queries would return nothing. Adopt 9 legend buckets aligned to the new boundaries (0, 1-20, 21-50, 51-100, 101-200, 201-300, 301-500, 501-2000, 2000+) so the panel makes use of the added 0-300 resolution.
Update the documented bucket array for tron:block_transaction_count to match the refined buckets in tronprotocol/java-tron#6730: [0, 20, 50, 80, 100, 120, 140, 160, 180, 200, 230, 260, 300, 500, 2000]. Per @Sunny6889's review on this PR.
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.
What does this PR do?
Add two new panel sections to the
java-tron-serverGrafana dashboard template to visualize the metrics introduced in tronprotocol/java-tron#6624:Block Metrics row (4 panels):
SR Set Change row (2 panels):
Why are these changes required?
tronprotocol/java-tron#6624 introduces
tron:block_transaction_count(histogram) andtron:sr_set_change(counter) metrics. This PR updates the official Grafana dashboard template so node operators can import and use the new panels directly, reducing onboarding effort as suggested in this comment.This PR has been tested by:
Follow up
Extra details
$group,$instance, backtick syntax,$__interval)