Eugen

@Kami @lakshmi-kannan We'll finally need `/health` endpoint for each st2 service like `auth`, `api`, `stream`. This is the case with running production-level StackStorm in K8s, but definitely would be helpful...

There are 2 paths to consider which was briefly discussed with @Kami: 1) Add health to existing API like: `/v1/stream/health`, `/v1/api/health`, `/v1/auth/health`. Need an option in st2.conf to disable auth...

Yes, after looking more into examples on how many other apps add this functionality (ex: [coreos/flannel](https://github.com/coreos/flannel/pull/722) and others), `/health` on a dedicated port (option 2) disabled by default makes sense...

Reassigning this to `3.0` milestone, per @Kami plans. Note that this was initially requested/proposed for `2.8`. Also would like to note that failing service fast on failure (like DB/MQ connection...

> Discovered during the K8s st2chatops work https://github.com/StackStorm/stackstorm-ha/pull/55 BTW here is an example of liveness http endpoint for `hubot`. This module when installed adds new endpoint `/health` https://github.com/joelwallis/hubot-health which is...

Transferred this feature request to the core `st2` repository. The `core.sendmail` action in question is: https://github.com/StackStorm/st2/blob/master/contrib/core/actions/sendmail.yaml

Quite valuable insights! Based on comments, I'm guessing it's https://github.com/StackStorm/st2/labels/wontfix

Following this logic, when you set the concurrency to `2`, - it really runs only `1` action at a time? Can you confirm that? Do those debug logs also indicate...

The StackStorm performance indeed has lots of bottlenecks and while we have an official K8s HA-focused deployment, it's important to keep in mind that platform was designed and created before...

Are your DBs/backends in K8s too? How's the setup is looking in there? If K8s is absolutely necesarry, - maybe worth trying the hybrid way, - keeping st2 pods in...