Drop /status endpoint

We’ve discussed the /health and /status endpoints quite a bit and we were planning to switch them. After some more thought I’m thinking a simple property to enabled/disable the full details on /health might be enough.

The status and health endpoint are so similar in code and concept that I think having them both might actually be confusing. I think offering a single endpoint with a switch might be enough for most users.

If a user is running behind a firewall they can set the property to expose more details. If they are not running behind a firewall they can either stick with hidden details, or configure securirty.

The only use-case we’ve not covered very well is someone getting an alert from an insecure /health and then wanting to get more details about which specific aspect caused the problem. That seems like a fairly edge case so I’m tempted to see of people complain first.

It’s pretty easy for us to re-introduce a new endpoint later. It’s much harder for us to take an existing one away.

[snicoll]

That seems like a fairly edge case so I’m tempted to see of people complain first.

This is a feature of 1.5.x that our users are using (given the number of complains we got that the configuration part was confusing). I don’t think dropping this is a good idea.

[snicoll]

@HaVonTe1 Thanks for the feedback, we discussed about this during our team meeting today and we believe we should at least reconsider some form of support. I’ve created #11869