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

Refactor client monitoring #5183

Merged
merged 7 commits into from
Feb 20, 2023
Merged

Conversation

nflaig
Copy link
Member

@nflaig nflaig commented Feb 20, 2023

Motivation

Some follow up changes/refactoring for #5037 to clean up few things and fix some minor issues.

Description

  • Simplify dynamic client stats property
  • Add 5 seconds bucket to collect data metric
  • Add 2 seconds to monitoring interval to avoid rate limit errors
  • Add comment on why only remote host should be logged
  • Override colors in send data duration panel
  • Add jsdoc to client stats properties
  • Use CONSTANT_CASE for client stats schema fixtures

See commits for further details.

@nflaig nflaig force-pushed the refactor-monitoring branch from 259ed76 to e85cc13 Compare February 20, 2023 13:19
- remove caching as it is currently unused, system data providers handle
the caching internally

- remove support for async provider functions, not needed at the moment
as all functions are synchronous
For some environments (e.g. windows) the collecting of system data might
take a bit longer. This bucket allows to get better insights on function
calls that took between 1-5 seconds.
@nflaig nflaig force-pushed the refactor-monitoring branch from e85cc13 to 6d149d2 Compare February 20, 2023 14:27
@nflaig nflaig marked this pull request as ready for review February 20, 2023 14:28
@nflaig nflaig requested a review from a team as a code owner February 20, 2023 14:28
Some calls randomly run into rate limiting, this might be due to delays when
collecting system data or other reasons which delay the previous request
which could let the next request run into a rate limit. It might also just
be due to a clock skew or other inaccuracies, it is hard to rely on time
between two remote systems. Adding 2 seconds seems to resolve this issue but
needs to be further observed.

The https://github.com/gobitfly/eth2-client-metrics-exporter also uses a
default interval of 62 seconds instead of 60 seconds.
Use color red for errors and color green for successful requests to remote service.
@nflaig nflaig force-pushed the refactor-monitoring branch from 6d149d2 to d0084dc Compare February 20, 2023 15:07
Copy link
Member

@wemeetagain wemeetagain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@wemeetagain wemeetagain merged commit d5343af into ChainSafe:unstable Feb 20, 2023
@philknows philknows added this to the v1.5.0 milestone Feb 20, 2023
@nflaig nflaig modified the milestones: v1.5.0, v1.6.0 Mar 4, 2023
@wemeetagain
Copy link
Member

🎉 This PR is included in v1.6.0 🎉

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

Successfully merging this pull request may close these issues.

3 participants