-
Notifications
You must be signed in to change notification settings - Fork 131
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
Send message through the bridge at least once per day #1840
Comments
@bkontur to send script to @svyatonik |
https://github.com/paritytech/devops/issues/2356
|
PR that will hopefully fix the missing files error: So we just need to wait and check the logs to see if it works |
Message from RBH to WBH is now sent every 6 hours. I've added an alert that should fire if there are no messages sent over last 24 hours, but it shows "No data" on our Grafana and I have no idea - why 😕 I'm gonna close this issue for now and track the alert separately. In any case - if messages will be sent, but not delivered, we shall see our regular errors |
* [ci] Fix publish benchmark results * Update scripts/ci/gitlab/pipeline/benchmarks.yml Co-authored-by: Sergejs Kostjucenko <85877331+sergejparity@users.noreply.github.com> * Update scripts/ci/gitlab/pipeline/benchmarks.yml Co-authored-by: Sergejs Kostjucenko <85877331+sergejparity@users.noreply.github.com> Co-authored-by: Sergejs Kostjucenko <85877331+sergejparity@users.noreply.github.com>
We have on-chain pallets. We have relay. We have monitoring stuff that gives us alerts if we are unable to deliver queued messages, relay headers, ... But what if noone sends any messages + we keep syncing mandatory relay chain headers, but actually something has broken in our bridge?
The suggestion is to send messages through the bridge (ideally in both directions), then if they are stuck, our monitoring shall detect that and give use alerts.
The text was updated successfully, but these errors were encountered: