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.

Sign up for GitHub

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

Jump to bottom

Tracking state of Chainhook Alarming #562

Closed
10 of 16 tasks
lgalabru opened this issue Apr 10, 2024 · 0 comments
Closed
10 of 16 tasks

Tracking state of Chainhook Alarming #562

lgalabru opened this issue Apr 10, 2024 · 0 comments
Assignees
@smcclellan
Milestone
Production Reliab...

Comments

@lgalabru
Copy link
Contributor

lgalabru commented Apr 10, 2024 •
edited by smcclellan
Loading

Chainhook side

The /ping or /status endpoint should expose:

  • Highest Bitcoin block height received (regardless if it is being connected to a fork)
  • Highest Bitcoin block height connected
  • Highest Bitcoin block height evaluated for predicates
  • Bitcoin Predicate Evaluation Lag (Highest Bitcoin block connected - Highest Bitcoin block evaluated for predicates)
  • Bitcoin Canonical Fork Lag (Highest Bitcoin block received - Highest Bitcoin block connected)
  • Highest Stacks block height received (regardless if it is being connected to a fork)
  • Highest Stacks block height connected
  • Highest Stacks block height evaluated for predicates
  • Stacks Predicate Evaluation Lag (Highest Stacks block connected - Highest Stacks block evaluated for predicates)
  • Stacks Canonical Fork Lag (Highest Stacks block received - Highest Stacks block connected)

Devops side (ticketed separately)

We want to trigger our alarming when:

  • Bitcoin Predicate Evaluation Lag > 1
  • Bitcoin Canonical Fork Lag > 1
  • bitcoind.block_height - chainhook.bitcoin.block_height > 1
  • Stacks Predicate Evaluation Lag > 1
  • Stacks Canonical Fork Lag > 1
  • stacks_node.block_height - chainhook.stacks.block_height > 1
@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Apr 10, 2024
@MicaiahReid MicaiahReid mentioned this issue Apr 10, 2024
Merged
@smcclellan smcclellan added this to the Production Reliability milestone Apr 11, 2024
MicaiahReid added a commit that referenced this issue Apr 12, 2024
@MicaiahReid
fix: correctly track bitcoin block append metrics; add additional met…
f85ac9e 
…rics (#563)

Addresses #562
github-actions bot pushed a commit that referenced this issue Apr 12, 2024
@semantic-release-bot
chore(release): 1.5.1 [skip ci]
065f9af 
## [1.5.1](v1.5.0...v1.5.1) (2024-04-12)

### Bug Fixes

* correctly track bitcoin block append metrics; add additional metrics ([#563](#563)) ([f85ac9e](f85ac9e)), closes [#562](#562)
@smcclellan smcclellan self-assigned this Apr 15, 2024
@smcclellan smcclellan moved this from 🆕 New to ✅ Done in DevTools Apr 17, 2024
vabanaerytk added a commit to vabanaerytk/chainhook that referenced this issue Aug 7, 2024
@vabanaerytk @semantic-release-bot
chore(release): 1.5.1 [skip ci]
d8b08f5 
## [1.5.1](hirosystems/chainhook@v1.5.0...v1.5.1) (2024-04-12)

### Bug Fixes

* correctly track bitcoin block append metrics; add additional metrics ([#563](hirosystems/chainhook#563)) ([d9ec3d7](hirosystems/chainhook@d9ec3d7)), closes [#562](hirosystems/chainhook#562)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smcclellan smcclellan

Labels
None yet
Projects
DevTools
Archived in project
Milestone
Production Reliability
Development

No branches or pull requests
2 participants
@lgalabru @smcclellan