Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Several Testnet metrics missing

Open
  • Is something wrong?
#14 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, grafana
Domain
observability-sre

Research direction

Start with the attached logs.txt from the Testnet validator running aleph-node 0.13.2 through Docker, then inspect the Grafana Dashboard queries for the two missing graphs. Compare the available metrics with the previous query using aleph_Imported, aleph_Ordering, aleph_Ordered, aleph_Aggregating, and aleph_Finalized; done means identifying the current metrics required to restore both graphs.

Written by the indexing model from the issue text.

Description

Did you read the documentation and guides?
  • I have inspected the documentation.
Is there an existing issue?
  • I have searched the existing issues.
Description of the problem

Since the last Testnet update r-13.0, I have noticed that metrics such as "aleph_Imported", "aleph_Ordering", "aleph_Ordered", "aleph_Aggregating" or "aleph_Finalized" are no longer available.

As a result, the graphs for "Block Time from Import to Finalized" and "AZERO Transactions per Second" are no longer displayed in the Grafana Dashboard.

Which metrics are now required to display the two graphs mentioned for the testnet? Mainnet does not seem to be affected.

For example, this is the query that was previously used to display the "Block Time from Import to Finalized" graph:
aleph_Imported + aleph_Ordering + aleph_Ordered + aleph_Aggregating + aleph_Finalized

I don't know if you really need but here is the log of the current running Testnet Validator:
logs.txt

Information on your setup.

  1. Running on testnet or mainnet?
    It affects the Testnet environment

  2. Version of aleph-node
    0.13.2

  3. How do you run aleph-node - directly, docker, aleph-node-runner?
    Through docker

  4. Is it a validator node or RPC-node?
    It's a validator node

  5. what flags do you run aleph-node with?
    I'm just using -n $VALIDATOR_NAME --ip $IP

  6. operating system
    Ubuntu 20.04

  7. hardware
    AMD Ryzen 9 3900 12-Core Processor, 128GB RAM, 2TB NVMe (RAID1)

Steps to reproduce

Start a Testnet Validator Node at least on Version r-13.0, when evaluating the metrics the mentioned metrics are no longer transmitted.

Did you attach relevant logs?
  • I have attached logs (if relevant).
Dominant language
No language data
Stars
2
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Cardinal-Cryptography/aleph-node-issues

All issues in Cardinal-Cryptography/aleph-node-issues

Similar issues

More Observability & SRE issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.