591706bd39
Move the hardcoded warn/crit cutoffs into Settings -> Thresholds (DB-backed, live, no restart). New thresholds.* keys + to_thresholds_cfg() + a threshold_style(value, kind) jinja global that reads them; latency reuses the existing ping good/warn keys, uptime is direction-aware (floors). Replace the _macros metric_style/uptime_style macros (now removed) with the global across Hosts-Overview, host_agent fleet + panel, Uptime/SLA widget, and the ping page uptime column — all now honor the configured cutoffs. Uptime keeps its green 'good' look when not degraded. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
20 lines
1.0 KiB
HTML
20 lines
1.0 KiB
HTML
{# settings/_tabs.html — include at top of each settings section #}
|
|
<h1 class="page-title">Settings</h1>
|
|
<div style="display:flex;gap:0;border-bottom:1px solid var(--border-mid);margin-bottom:1.5rem;">
|
|
{% set tabs = [
|
|
("general", "General", "/settings/general/"),
|
|
("thresholds", "Thresholds", "/settings/thresholds/"),
|
|
("notifications", "Notifications", "/settings/notifications/"),
|
|
("reports", "Reports", "/settings/reports/"),
|
|
("auth", "Auth", "/settings/auth/"),
|
|
("ansible", "Ansible", "/settings/ansible/"),
|
|
("plugins", "Plugins", "/settings/plugins/"),
|
|
] %}
|
|
{% for key, label, href in tabs %}
|
|
<a href="{{ href }}"
|
|
style="padding:0.6rem 1.1rem;font-size:0.875rem;border-bottom:2px solid {{ 'var(--accent)' if active_tab == key else 'transparent' }};color:{{ 'var(--text)' if active_tab == key else 'var(--text-muted)' }};font-weight:{{ '500' if active_tab == key else 'normal' }};text-decoration:none;">
|
|
{{ label }}
|
|
</a>
|
|
{% endfor %}
|
|
</div>
|