JD

I am not sure if you initiated an issue, but it looks like your service pxc became UNHEALTHY after rancher-alarms started. Here are my logs. As you can see 6...

Using the rancher cli running a `ps` against the environment shows every service and sidekick as healthy. What is rancher-alarms querying to check for a healthy state?

Also, using the "view in API" from the UI is showing the same results - active and healthy.

There is only a single cattle environment on the server that is being queried.

@VAdamec - I found the issue and it does have to do with the version of Rancher. The `_withoutSidekicks` function does a split on the container name using an underscore....