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

[monitoring] Regular run + monitoring of the system-tests #3172

Open
nutrina opened this issue Jan 9, 2025 · 0 comments
Open

[monitoring] Regular run + monitoring of the system-tests #3172

nutrina opened this issue Jan 9, 2025 · 0 comments

Comments

@nutrina
Copy link
Collaborator

nutrina commented Jan 9, 2025

User Story

As a passport developer
I want the system tests to be executed on a regular basis (once every 5 minutes)
Such that I can verify the health status of our service in a superset dashboard and in uptime robot

Acceptance Criteria

GIVEN I open the "service health" dashboard
WHEN when I go to the service health dashboard
THEN I can see the overall status of the last 100 runs of the system-test runs
AND drill down into individual tests to check for the status (or errors)

GIVEN the system tests are in place
WHEN a run of the system tests is not succesfull
THEN the on-call engineer is receiving a pagerduty notification via uptime robot

Technical details

  • for uptime robot to be able to pull the status of the last system-tests run, we shall implement a public API that returns the status & timestamp of the last test run
    • we consider the system to be in an error state if:
      • the last test run failed
      • or the last test run was over 10 minutes ago (feel free to suggest another threshold)
@nutrina nutrina converted this from a draft issue Jan 9, 2025
@nutrina nutrina changed the title [monitoring] Regular run of the system-tests [monitoring] Regular run + monitoring of the system-tests Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Prioritized
Development

No branches or pull requests

1 participant