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

SLA uptime always red with IndyScan test outages #201

Open
loneil opened this issue Aug 27, 2024 · 3 comments
Open

SLA uptime always red with IndyScan test outages #201

loneil opened this issue Aug 27, 2024 · 3 comments

Comments

@loneil
Copy link

loneil commented Aug 27, 2024

We have 2 uptime monitoring dashboards
https://ditp.uptime.vonx.io/?start=20240729&end=20240827
https://ditp.sla.vonx.io/?start=20240729&end=20240827

The second SLA one is red every day due to "BCovrin IndyScan Sync - Test" never being above the threshold.
https://ditp.sla.vonx.io/statuspage/ditp.sla/2714146?start=20240827&end=20240827

image

Should probably remove it or adjust that threshold if it's not important for an SLA to track (or if it is important enough and has to not be down daily would need a fix)

@WadeBarnes
Copy link
Member

I've adjusted the SLAs on BCovrin - Test and BCovrin IndyScan Sync - Test

@WadeBarnes
Copy link
Member

I've decided to remove BCovrin IndyScan Sync - Test from the SLA page completely. The BCovrin IndyScan Sync - Test monitor is really intended as an alert to indicate when BCovrin IndyScan Sync - Test is out of sync with the ledger for an extended period of time. BCovrin IndyScan Sync - Test will always get out of sync with the ledger for a period of time when there's a high transaction volume, and this happens every evening for a few hours when the ACA-Py integration test kick off.

Removing BCovrin IndyScan Sync - Test from the SLA page cleans things up significantly providing a clearer picture.

image

@WadeBarnes
Copy link
Member

@loneil, Have a look and see what you think. We can further refine the SLAs of each of the monitors or the services listed on the page as needed.

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

No branches or pull requests

2 participants