Skip to content

feature request Per-check custom color + priority ordering for failure visualization #2467

Description

@doubleclic32

Description

Currently, all failing checks are rendered with the same red color regardless of their nature. I'd like the ability to assign a custom color to each individual check, and to define a priority order among checks so that when an agent has multiple failing checks at once, the agent's status badge can display the color of the highest-priority one.

Current behavior

  • All failing checks: same red
  • No way to distinguish a critical outage from a less urgent issue (e.g. expired Windows activation, missing optional service, etc.)
  • When an agent has several failing checks, no concept of which one matters most

Proposed behavior

  1. Per-check color: each check can be assigned a custom color (hex code or palette pick) via the check's settings page.
  2. Check priority / ordering: introduce an ordered list of checks (drag-and-drop in the UI, or a numeric priority field). The check at the top of the list has the highest priority.
  3. Resolution rule for the agent status badge:
  • Among the failing checks for an agent, pick the one with the highest priority
  • Display its color on the agent's row / status badge
  • The other failing checks remain visible in the agent detail with their own colors
  1. Optional: a fallback color when no per-check color is defined (preserves current red).

Why per-check (not per check_type)

Two script checks can have very different meaning (one detects a missing antivirus, another detects an expired license). Coloring only by check_type would force both to share a color, defeating the purpose.

Why priority

Without an ordering, the agent badge can only show one color, but an agent often has several failing checks simultaneously. Priority resolves the ambiguity deterministically.

Migration / compatibility

Additive: existing setups keep the current red. Color and priority default to "unset", in which case the legacy behavior applies.

Happy to contribute a PR if helpful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions