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

Send message through the bridge at least once per day #1840

Closed
svyatonik opened this issue Feb 1, 2023 · 4 comments
Closed

Send message through the bridge at least once per day #1840

svyatonik opened this issue Feb 1, 2023 · 4 comments
Assignees
Labels
A-chores Something that has to be done, as part of regular maintenance P-Devops R-W Bridge Dependency Deploy

Comments

@svyatonik
Copy link
Contributor

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.

@EmmanuellNorbertTulbure
Copy link

@bkontur to send script to @svyatonik

@bkontur
Copy link
Contributor

bkontur commented Mar 7, 2023

@svyatonik
Copy link
Contributor Author

PR that will hopefully fix the missing files error:
https://gitlab.parity.io/parity/infrastructure/parity-testnet/-/merge_requests/941

So we just need to wait and check the logs to see if it works

@svyatonik
Copy link
Contributor Author

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

svyatonik pushed a commit that referenced this issue Jul 17, 2023
* [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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chores Something that has to be done, as part of regular maintenance P-Devops R-W Bridge Dependency Deploy
Projects
None yet
Development

No branches or pull requests

3 participants