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

Alert that will fire if we are not running relayer #1999

Closed
svyatonik opened this issue Mar 28, 2023 · 0 comments · Fixed by #2002
Closed

Alert that will fire if we are not running relayer #1999

svyatonik opened this issue Mar 28, 2023 · 0 comments · Fixed by #2002
Assignees
@svyatonik
Labels
A-chores Something that has to be done, as part of regular maintenance
Milestone
Kusama <> Polkado...

Comments

@svyatonik
Copy link
Contributor

Right now all our alerts are relying on data that is read from relayer. Unfortunately due to some internal issues, I had to set the when NoData -> Set to OK option for all those alerts. But what if there's no relayer at all? Then alerts will be OK, because of this setting && we won't get any notifications.

Ideal solution is to read data (e.g. best known bridged chain blocks) directly from chains - see #2471. Other option is to have other alert that will fire if our relayer is not running.
@svyatonik svyatonik added the A-chores Something that has to be done, as part of regular maintenance label Mar 28, 2023
@svyatonik svyatonik self-assigned this Mar 28, 2023
@svyatonik svyatonik mentioned this issue Mar 29, 2023
Merged
Closed
34 tasks
svyatonik pushed a commit that referenced this issue Jul 17, 2023
@bkontur
Bridge hub kusama fine-tuning before release (#1999)
489a5b5 
* Fix benchmarks-ci.sh - missing pallet_utility/pallet_multisig

* Missing ParentAsSuperuser for bridge-hubs

* Fixed missing stuff in benchmarks.yml

* Added MigrateToTrackInactive + CheckingAccount (for completness as other runtimes)

* Measured xcm weights for bridge-hubs

* Fix for fungible benchmarks

* ".git/.scripts/bench-bot.sh" xcm bridge-hub-kusama bridge-hubs pallet_xcm_benchmarks::fungible

* ".git/.scripts/bench-bot.sh" xcm bridge-hub-rococo bridge-hubs pallet_xcm_benchmarks::generic

* ".git/.scripts/bench-bot.sh" xcm bridge-hub-rococo bridge-hubs pallet_xcm_benchmarks::fungible

* ".git/.scripts/bench-bot.sh" xcm bridge-hub-kusama bridge-hubs pallet_xcm_benchmarks::generic

* Reverting migrations - no need for them

* script for generate genesis spec/head/wasm

* Adding invulnerables and session.keys to the script
(paritytech/devops#2196)

* update chainspec with cmd: ./scripts/create_bridge_hub_kusama_spec.sh ./target/release/wbuild/bridge-hub-kusama-runtime/bridge_hub_kusama_runtime.compact.compressed.wasm 1003

* para_id 1003 -> 1002, cmd: ./scripts/create_bridge_hub_kusama_spec.sh ./target/release/wbuild/bridge-hub-kusama-runtime/bridge_hub_kusama_runtime.compact.compressed.wasm 1002

Co-authored-by: command-bot <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svyatonik svyatonik

Labels
A-chores Something that has to be done, as part of regular maintenance
Projects
None yet
Milestone
Kusama <> Polkadot Parachain Bridge R...
Development

Successfully merging a pull request may close this issue.

Relay node down alert paritytech/parity-bridges-common
1 participant
@svyatonik