Implement Tenderly Web3 Actions to monitor different RedStone smart contracts #212
Conversation
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
matjazv
changed the title
matjazv
force-pushed
the
LISK-1157-Set-up-alerts-on-Tenderly-and-or-Elastic
branch
from
7d5eaa5 to
148ecd0
Compare
sameersubudhi
requested changes
Nov 18, 2024
matjazv
force-pushed
the
LISK-1157-Set-up-alerts-on-Tenderly-and-or-Elastic
branch
from
4d01af8 to
f1ce796
Compare
|
@sameersubudhi |
sameersubudhi
approved these changes
Nov 18, 2024
Incede
approved these changes
Nov 18, 2024
sameersubudhi
deleted the
LISK-1157-Set-up-alerts-on-Tenderly-and-or-Elastic
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was the problem?
This PR resolves #LISK-1157.
How was it solved?
USDT/USD,LSK/USDandETH/USDtoken pairs were created to monitor their updateHow was it tested?
Web3 Actions for all three token pairs were deployed to Tenderly and they were manually executed to check if alerts inside Opsgenie were created.