8 Commits

Include renames

Author	SHA1	Message	Date
jaredandClaude Opus 5.5	d07787ee38	Monitor: keep checking interfaces whose link-down alert is still open ... After the interface baseline is reset, a port that is already down reads as "first seen down", which neither alerts nor resolves. An alert opened before the reset was then stuck open without updates: micro1's enp3s0 had sat at one failed check since March with no ticket. An interface with an open interface_down alert is now treated as previously up, so the alert keeps counting, tickets and resolves as normal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-11 01:02:53 -05:00
jaredandClaude Opus 5.5	c262e5ecc8	Inventory links, cutsheet marks on faceplates, and single page titles ... Device pages get an Inventory button: it opens the device's HomeBox record once an admin pastes its URL (stored in the new device_links table; only URLs on inventory.base_url are accepted), and searches the inventory for the model until then. Tickets link the record too. Faceplate ports with a documented cable get a corner dot: green matches, red mismatch, grey documented but unconfirmed. The port's tooltip names the cable, and a legend toggle (remembered per browser) hides them. Page titles no longer repeat GANDALF ("Alert History - GANDALF - GANDALF"). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 20:47:14 -05:00
jaredandClaude Opus 5.5	437f7a415f	Add recovery notes and fuller context to tickets ... When an alert that opened a ticket clears, the monitor now comments on the ticket (when it cleared, how long it lasted, failed checks, a link back). It never closes or changes a ticket's status. Failed notes retry each cycle for 24 hours; a 401/403 from Tinker stops them until restart. Tickets are now Markdown with a "What to check" list and, where known: the switch port the device plugs into (kept from the last time it was seen, so a dead host still shows it), cutsheet cables and their path, how often the alert fired in the last 7/30 days, other open alerts on the device, and links into Gandalf (gandalf.public_url). Titles are unchanged so Tinker's duplicate detection still works. network_events gains recovery_notified, added at monitor startup; rows that cleared before the upgrade count as already notified. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 19:44:50 -05:00
jaredandClaude Opus 5.5	86aa29b378	Cutsheet trace mode and mismatch alerts ... Trace a cord: pick a panel port, press Start, and unplug the cord at the panel. The page polls a new admin-only endpoint that reads every switch port's state from UniFi (cached 2 s), shows the one port that dropped with a button to record the cable, and confirms when it's plugged back in. Several ports dropping at once, or none within 3 minutes, is explained rather than guessed at. Mismatch alerts: the monitor runs the cutsheet check every poll. Each mismatched installed run (wrong neighbor, no link, missing port, port conflict) keeps one cable_mismatch event on its switch, resolved when fixed, and opens a P4 ticket after cutsheet.mismatch_ticket_hours (default 24, 0 never). Suppressing the switch or port stops the ticket. Also fixes buttons with the hidden attribute still showing, which left a Delete button on the new-cable form. Closes #12 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 16:54:57 -05:00
jaredandClaude Opus 5.5	7e588e5b02	Keep every switch port and show SFP modules ... Ports were keyed by their UniFi name, so when two ports shared a name the later one replaced the earlier. The 24-port switch lost port 13 this way (ports 13 and 14 are both "Office TV"). A repeated name is now kept as "<name> (Port N)". Traffic rates are now matched to the previous poll by port number rather than name. Names are re-read from UniFi every poll, so a port renamed there keeps its rates instead of losing them for a cycle. Collect what UniFi reports about each SFP cage: whether a module is present, its type (DAC or optic), part, serial, fault flags, and DOM readings when the module has them. The faceplate draws empty cages, optics, DACs and unidentified modules differently and outlines a faulted module in red. The port panel gets an SFP Module section. Both ends of a DAC report the same cable serial, so each end links to the other. Closes #7 Closes #8 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-10 14:37:08 -05:00
jaredandClaude Opus 5.5	178a03e898	Give hosts longer before ticketing them as gone ... A host's node_exporter stops as soon as a shutdown begins and a normal reboot takes about 3-5 minutes, so the 2-check failure_threshold cut a ticket for planned reboots. Add monitor.host_failure_threshold, default 5, for hosts with no metrics and ping-only hosts. Interface link-down alerts keep the shorter threshold, and the dashboard still shows the host as down straight away. Closes #14 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-06 19:35:50 -05:00
jaredandClaude Opus 5.5	bdcfb76c25	Move the port inspector onto device pages ... Replace the all-switches Inspector page with a per-device front panel, port table and detail panel. /inspector now redirects to the dashboard, and /device/<name>#port-<n> links directly to a port. Restore neighbor names after UniFi's LLDP change: read local_port_idx and resolve neighbors by MAC using Prometheus NIC data, UniFi devices and the wired client table. This also brings back Run Diagnostics on server ports, which depends on a named neighbor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-05 10:11:11 -05:00
jaredandClaude Opus 5.5	e32499b7f6	Add AT&T modem monitoring and device pages; replace Link Debug ... Modem and WAN: - Poll the BGW320 status pages read-only for light levels, PON and WAN state, with a WAN / Fiber panel, 7-day Rx trend, and alerts on WAN down, optical limits, and Rx drift - Read WAN outages and Smart Power restarts from the UniFi system log, since outages can be over between 5 minute polls Device pages: - Add device search to the dashboard and a page per host, switch, router, AP, PDU, or modem - Move all Link Debug data into expandable rows there; /links redirects - Collect UDM ports and UniFi device details (firmware, load, WAN, outlets) - Reorder the dashboard Monitoring fixes: - Alert when a configured host stops reporting: its series disappear rather than reporting down, so a dead host never raised an alert - Alert on Prometheus outages instead of blanking the dashboard - Treat a failed Pulse ping as unknown rather than host unreachable - Stop new switch ports reporting lifetime bytes as one interval's rate - Run database sessions in UTC: other server time zones shifted displayed ages and timed suppression expiries Also log every avatar 404 reason, add a favicon, and correct the WAN link labels (1G on Port 9, not 10G SFP+). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-04 23:40:17 -05:00