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

Add metric for every step on the pipeline #2

Open
kaisbaccour opened this issue Apr 13, 2023 · 3 comments
Open

Add metric for every step on the pipeline #2

kaisbaccour opened this issue Apr 13, 2023 · 3 comments

Comments

@kaisbaccour
Copy link
Contributor

  • beacons_request_inclsuion_in_customer_chain_time
  • relay_and_job_subscription_time
  • drand_wait_time
  • verification_time
  • relay_and_block_inclsuion_in_customer_chain_time
@webmaster128
Copy link
Contributor

This means many different histograms, right? So far we have just two, the e2e time and the processing time (i.e. the part we can control).

@kaisbaccour
Copy link
Contributor Author

kaisbaccour commented May 8, 2023

This means many different histograms, right? So far we have just two, the e2e time and the processing time (i.e. the part we can control).

Yes indeed so probably 5 histograms. Then the timing out task would get the max_integer.
We could eventually add the ics20 transfer time but that's probably not as important.
For the gateway step we need to make sure that the job enqueue step can happen before the drand release.

Next to this we need to make a list of what visualisations/dashboards we want to see on grafana.

@webmaster128
Copy link
Contributor

When we track all of this data, we need to ensure to not stack the histograms. Some of them track overlapping times such as relaying to the gateway and waiting for the drand.

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

2 participants