This repository has been archived by the owner on May 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Create relay-meter-service.md #9
Open
adshmh
wants to merge
1
commit into
main
Choose a base branch
from
relay-meter-replacement-v0
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
TxDB as replacement for relay-meter | ||
|
||
```mermaid | ||
flowchart | ||
|
||
%% TxDB Service | ||
%% ------------------------------------- | ||
subgraph txdbs [TxDB Service] | ||
receiver(Relay Metrics Receiver) | ||
pgA[(Central Postgres DB)] | ||
aggA(Metrics Aggregator) | ||
persistenceA[(Aggregated Metrics Persistence)] | ||
meterA(Relay Metrics Reporter/relay-meter replacement) | ||
|
||
receiver-->pgA | ||
receiver-->aggA | ||
aggA-->persistenceA | ||
aggA-->meterA | ||
|
||
end | ||
|
||
%% Portal Region 1 | ||
%% ------------------------------------- | ||
subgraph pi1 [Portal Region 1] | ||
relayer1(Relayer) | ||
lim1(Rate-Limit Enforcement Plugin) | ||
metrics1(Metrics Recorder) | ||
pubsub1(Regional Portal Pubsub Service/NATS) | ||
tx1(TxDB Pubsub Service: Reports Relay Metrics to TxDB) | ||
|
||
metrics1-->pubsub1 | ||
pubsub1-->tx1 | ||
relayer1-->metrics1 | ||
lim1-->relayer1 | ||
end | ||
|
||
%% Portal Region 2 | ||
%% ------------------------------------- | ||
subgraph pi2 [Portal Region 2] | ||
relayer2(Relayer) | ||
lim2(Rate-Limit Enforcement Plugin) | ||
metrics2(Metrics Recorder) | ||
pubsub2(Regional Portal Pubsub Service/NATS) | ||
tx2(TxDB Pubsub Service: Reports Relay Metrics to TxDB) | ||
|
||
relayer2-->metrics2 | ||
metrics2-->pubsub2 | ||
pubsub2-->tx2 | ||
lim2-->relayer2 | ||
end | ||
|
||
subgraph rateLimiter [Rate-Limiter] | ||
rateLimiterCollector(Relay Metrics Collector) | ||
rateLimitsPublisher(Rate-Limit List Publisher) | ||
|
||
rateLimiterCollector-->rateLimitsPublisher | ||
end | ||
|
||
|
||
%% Connections between subgraphs | ||
%% ------------------------------------- | ||
tx1-->receiver | ||
meterA-->rateLimiterCollector | ||
rateLimitsPublisher-->lim1 | ||
|
||
tx2-->receiver | ||
rateLimitsPublisher-->lim2 | ||
``` |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One think to take into account is that the tx db service does not hold specific info regarding rate limiting, it holds data of all relays which then is aggregated to data warehouse in multiple ways, one of them being available for rate limiting. What I mean is that tx db service does not have special data structures specific for rate limiting, so all the code for this will be made in a way that this is only presented as a reporting service, which then can be consumed by services like rate limiter