Date: 2026-02-18 • Alarm: Technology Wise Site Down • Full 24-Hour Analysis
Venn-style breakdown of sites appearing in each system
How many sites match vs differ between systems
SiteWatch has 3.4x more rows but only 0.53x the unique alarm events
Most alarms clear within 15 minutes — invisible to SiteWatch polling
Per-site difference in alarm count — positive = NetPulse sees more
Most sites have 1-3 alarms; flapping sites can have 100+
SiteWatch polls every 15 minutes. NetPulse records every raise/clear cycle. Since 79.4% of NetPulse alarms last less than 15 minutes, they fall entirely between two SiteWatch polling windows and are never captured.
NetPulse records every re-occurrence separately. Site AGQ8168 has 176 NetPulse records but only 4 SiteWatch events. 951 sites show duplicate FirstOccurred timestamps, totaling 4,401 flapping records.
SiteWatch repeats each active alarm across polling batches. An alarm active for 4 hours generates ~16 rows. This inflates SiteWatch's raw count to 33,955 rows for only 5,298 unique events.
63 SiteWatch-only sites have alarms originating before Feb 18 (some from Jan 6). NetPulse scopes to alarms with FirstOccurred on Feb 18, so these long-running alarms are excluded from NetPulse.
NetPulse = new alarms raised per hour • SiteWatch = unique active sites per hour
A massive spike of 1,860 alarms at 16:00 in NetPulse — over 3x the hourly average. SiteWatch shows a smaller peak (~985 sites), confirming most of these were very short-lived flaps.
Both systems show a secondary spike at 01:00 (~865 alarms). This suggests a scheduled nightly process (maintenance window, batch job, or power cycling) affecting many sites.
SiteWatch shows a gradual rise from 13:00–16:00, reflecting alarms that accumulate and persist. NetPulse shows sharper spikes, capturing the rapid fire-and-clear pattern typical of transient issues.
Percentage of common sites where alarm counts match, NetPulse is higher, or SiteWatch is higher
Click column headers to sort
| Region | Total Sites | Exact Match | Match % | NetPulse Higher | NetPulse Higher % | SW Higher | SW Higher % |
|---|
Only 56% match rate with 41% showing NetPulse higher. South has the most sites (1,773) and the most alarm flapping, suggesting infrastructure instability in southern regions.
79% match rate — best among all regions. Fewer transient alarms indicate more stable infrastructure or less sensitive alarm thresholds.
Points on the diagonal line = perfect agreement • Points above = SiteWatch higher • Points below = NetPulse higher
Search, filter, and sort all sites across both systems
| Site ID | Region | City | NetPulse Alarms | SW Events | SW Rows | Difference | Short (<15m) | Status |
|---|
SiteWatch's 15-minute polling window misses roughly 40% of alarm events that NetPulse captures. Any alarm that raises and clears within a single polling cycle is invisible to SiteWatch. This is the single biggest driver of the count disparity.
SiteWatch records the state of each active alarm at every 15-minute batch (95 batches/day). A single alarm active for 6 hours generates ~24 rows. The raw row count is 3.4x higher than NetPulse, but unique events are only 0.53x.
NetPulse answers: "How many times did alarms fire?" (event-centric, captures every flap)
SiteWatch answers: "How many alarms were active at each time window?" (state-centric, captures duration)
Compare NetPulse alarm counts against SiteWatch's unique source_event_time per site, not raw row counts. This gives 63% exact match for common sites, and the remaining differences are primarily short-lived flapping alarms.
Sites like AGQ8168 (176 NetPulse records vs 4 SW events) indicate unstable network elements that go down and come back within minutes, repeatedly. These are candidates for proactive maintenance. The South region has the highest concentration of flapping sites.
SiteWatch snapshots all currently-active alarms regardless of origin date. NetPulse scopes to FirstOccurred on the analysis date. For a complete picture, combine both views: NetPulse for new events, SiteWatch for ongoing state.