Sluicio v0.11.60

A dashboard can hold a system

Dashboards could pin integrations and services. Systems — the thing that has members, its own health checks, and its own rolled-up status — could not go on a board at all, even though they are peers of integrations everywhere else in the product.

They can now. edit dashboard offers add system, listing your systems with their member counts. The card shows the system's type, its health, and how many services it covers, and clicks through to the system.

Only integrations and systems

The old add system picker actually listed services flagged as a system. Wrong label, and off-model: this is an integration-centric product, and a board holds integrations and systems.

That picker is gone. Cards created by it are untouched — they still render and can still be removed, under a strip now labelled System services so the two never read alike. Nothing was converted or deleted: mapping a flagged service onto a system means guessing, and it may belong to none.

The card reports health, it does not guess

The card shows the status the server computes, which already folds in the checks bound to the system itself. A browser cannot see those checks, so anything recomputing health in the page calls a system with a firing check quiet — the failure fixed across four surfaces in v0.11.56–58. This card does not recompute.

Fixes

• The remove × on a system card did nothing outside edit mode. It was offered on every system card, but outside edit mode the page renders the saved dashboard while the button edited a draft — so the card sat there and nothing saved. It is now edit-mode only, matching the integration card.
• last could not be chosen when editing a health check. The health-check editor offered seven aggregation functions; the metrics builder offered nine. The two missing were last and age — and last is the only correct function for a point-in-time gauge, so a check on an HTTP status code could not be expressed at all, though the server has always accepted it and ships templates using it. Both pickers now share one list.
• Pinning a system from another organisation is refused at the API rather than accepted and rendered as a permanently blank card.
• A card whose system was deleted still renders, marked no longer exists, so it can be removed.

Also

Paperless-ngx is recognised as a system type, with monitoring templates and a documentation page at docs.sluicio.com/system-types/paperless-ngx.