Skip to content

validate api script (#10217) #10220

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

validate api script (#10217) #10220

wants to merge 2 commits into from

Conversation

ReynardoEW
Copy link
Member

@ReynardoEW ReynardoEW commented Jul 21, 2025

uses api-docs schemas, some error caused by wrong schemas definition so need to make changes there #10217

.env setting
BASE_API_URL=https://api.llama.fi
BETA_API_URL=
DISCORD_WEBHOOK_URL=
PRO_API_KEY=

@ReynardoEW ReynardoEW requested a review from g1nt0ki July 21, 2025 06:43
@treeoflife2 treeoflife2 self-requested a review July 25, 2025 09:50
@treeoflife2
Copy link
Member

@ReynardoEW are we sending the json file in the discord? as discord message will be truncated when it's very big? everything else looks good.

@ReynardoEW
Copy link
Member Author

@ReynardoEW are we sending the json file in the discord? as discord message will be truncated when it's very big? everything else looks good.

it send summaries not full json file something like this


pro api:
• total endpoints: 82
• pass: 77
• fail: 5
• success rate: 93.9%
• avg resp time: 1401ms

failed endpoints (5 of 5):
1. https://pro-api.llama.fi/api/emission/hyperliquid
2. https://bridges.llama.fi/bridgevolume/Ethereum?id=5
3. https://bridges.llama.fi/bridgedaystats/1667304000/Ethereum
4. https://bridges.llama.fi/transactions/1?starttimestamp=1667260800&endtimestamp=1667347200&sourcechain=Polygon&address=ethereum%3A0x69b4B4390Bd1f0aE84E090Fe8af7AbAd2d95Cc8E&limit=200
5. https://pro-api.llama.fi/coins/block/sample/sample

2025-07-21T06:19:06.323Z```

@treeoflife2
Copy link
Member

@ReynardoEW it will only send the alert if there is failure right? imo json file would be better for debugging, but we can add it later if needed for jenkin jobs, or we can add link of file, as i believe filename will always same we can later use static link, but fine for now.

@ReynardoEW
Copy link
Member Author

@ReynardoEW it will only send the alert if there is failure right? imo json file would be better for debugging, but we can add it later if needed for jenkin jobs, or we can add link of file, as i believe filename will always same we can later use static link, but fine for now.

@ReynardoEW it will only send the alert if there is failure right? imo json file would be better for debugging, but we can add it later if needed for jenkin jobs, or we can add link of file, as i believe filename will always same we can later use static link, but fine for now.

i have updated it to only send when error, yes i also think sending json link is better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants