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

BUG: Public API endpoint unknown to health monitoring alerts. #6903

Closed
9 tasks
adunkman opened this issue Oct 26, 2020 · 3 comments
Closed
9 tasks

BUG: Public API endpoint unknown to health monitoring alerts. #6903

adunkman opened this issue Oct 26, 2020 · 3 comments
Assignees
Labels

Comments

@adunkman
Copy link

Describe the Bug

There is no single Public API endpoint for the health endpoint which health alerts can be configured to monitor.

Business Impact/Reason for Severity

The Court Tech Lead needs to be notified when the application reports an unhealthy system status, and without a machine-readable endpoint, health alerts cannot be configured to send such notifications.

Similar to #6864, but for the public API.

In which environment did you see this bug?

https://stg.ef-cms.ustaxcourt.gov/health

Who were you logged in as?

N/A

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)

Working on ustaxcourt#250.

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://stg.ef-cms.ustaxcourt.gov/health
  2. Observe there is no single API endpoint — there are two used, the UI accesses either:

Expected Behavior

I expected the API to be accessible at https://public-api.stg.ef-cms.ustaxcourt.gov/

Actual Behavior

There are two API endpoints used, either public-api-blue.stg.ef-cms.ustaxcourt.gov or public-api-green.stg.ef-cms.ustaxcourt.gov. The UI has prior knowledge to determine which endpoint to access, which the configured Route53 Health Checks do not have.

Cause of Bug, If Known

The implementation of a blue/green deploy strategy removed this endpoint.

FOR ENGINEERING TEAM ONLY
Bug Resolution Steps:

  • Determine why the bug wasn't caught by a test.
  • Determine if an automated test needs to fixed, expanded or created. If unsure, bring in others to discuss.
  • Determine if a manual test needs to be fixed, expanded or created. If unsure, bring in others to discuss.
  • If needed, automated test is created.
  • If needed, manual test is created.
  • Reason for bug has been documented.
  • Fix has been deployed to dev environment.
  • Fix has been deployed to the stage environment.
  • Bug has been tested in staging (UX or Engineering).
@codyseibert
Copy link

EOD update: I managed to get most of the terraform code deployed to exp1, now I need to verify it works.

@JessicaMarine JessicaMarine added the bug Something isn't working label Dec 2, 2020
@codyseibert
Copy link

To verify, you could go to https://public-api.dawson.flexion.us/public-api/health

@adunkman
Copy link
Author

adunkman commented Dec 2, 2020

Implemented in #7177, not yet included in a PR to the Court’s repo.

Looks great! Thanks @codyseibert!

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

No branches or pull requests

5 participants