-
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
Adjust monitoring for new deployment setup #3004
Comments
@bkontur Most of dashboards are working fine. E.g.: This "No data" is maybe because the metric name has changed to e.g. |
I see now, why all the dashboards are empty for metric: Because we run We don't run those metrics for standalone relaying: relayer-headers or relay-parachains or relay-messages. It would be nice to add those metrics for all relayings as on-demand, so the relayer can say with cli argument to add or not those metrics. Till the time we fix this (or remove those alerts/dashboards), I am pausing those alerts: |
Closes: #7272 Relates to: #6578 Relates to: #7274 ## Description The PR enhances the `pallet-bridge-rewards` by making it generic over the `RewardKind` type (previously hardcoded as `RewardsAccountParams`). This modification allows the pallet to support multiple reward types (e.g., P/K bridge, Snowbridge), increasing its flexibility and applicability across various bridge scenarios. Other pallets can register rewards using `bp_relayers::RewardLedger`, which is implemented by the rewards pallet. The runtime can then be configured with different mechanisms for paying/claiming rewards via `bp_relayers::PaymentProcedure` (e.g., see the `pub struct BridgeRewardPayer;` implementation for BridgeHubWestend). ## Follow-up The removed balances/rewards statistics from the complex relay (no longer used) will eventually be reintroduced or fixed in the standalone relayers via paritytech/parity-bridges-common#3004 (comment). --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Francisco Aguirre <[email protected]> Co-authored-by: Serban Iorga <[email protected]>
The text was updated successfully, but these errors were encountered: