Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

/health and /status disparity #2

Open
abrahammartin opened this issue Feb 22, 2018 · 1 comment
Open

/health and /status disparity #2

abrahammartin opened this issue Feb 22, 2018 · 1 comment

Comments

@abrahammartin
Copy link
Member

We need to revisit the /health and /status disparity and make them better, we need to rely on 1 single unique point for all our apps to create consistency. Maybe using parameters, etc.

From PR #1

@rjw57
Copy link
Member

rjw57 commented Feb 28, 2018

As an additional note: using the /status endpoint means our logs get filled with database connection messages every second. We should see if we can make the cloud-sql-proxy a little less noisy.

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

No branches or pull requests

2 participants