Service error states not immediately visible in admin UI

Steps to reproduce

Steps to reproduce:

1. Create an error state in a service (e.g. incorrect config)
2. Notice that some jobs are not running
3. Go to System / Services

Actual Results:

The default sort order means that a long list of NORMAL services is shown, and you have to explicitly sort by Status to see that one is in ERROR.

Expected Results:

1. There should be a global visual indicator in the UI that one or more services is in ERROR state (e.g. exclamation mark or alert message)

2. When you go to the Services page, the default sort order should be to show services in ERROR.

Workaround (if any):

Be vigilant, and sort by Status.


Greg Logan
August 23, 2017, 9:12 PM

The default sort order is aleady set in 4.x, but not in 3.x. Backporting the indicator code from 4.x appears to be relatively trivial, will ask on list.

Greg Logan
August 23, 2017, 8:13 PM

Changing the default sort order is trivial, but adding a global visual indicator is trickier. That indicator doesn't make it appearance until 4.x. I can try backporting it, but I suspect that it might be considered a new feature for the 3.x branch.

Fixed and reviewed
Your pinned fields
Click on the next to a field label to start pinning.


Greg Logan


Stephen Marquard


Usability Issue