Files
pulse/mock.env.good
T
Pulse Monitor 0aeeb3da0d fix: resolve alert acknowledgment timeout issue (addresses #438)
The alert acknowledgment endpoints were hanging because GetState() was called
synchronously to broadcast updates via WebSocket, which could take significant
time with many nodes/guests. This caused the HTTP response to timeout, showing
an error to users even though the alert was successfully acknowledged.

Fixed by:
- Sending HTTP response immediately after acknowledging the alert
- Moving WebSocket broadcast to a goroutine to avoid blocking
- Applied fix to all alert endpoints (acknowledge, unacknowledge, clear, bulk ops)

This resolves the issue where users saw 'Failed to acknowledge alert' errors
but the alert was actually acknowledged (disappeared on refresh).
2025-09-10 15:49:12 +00:00

31 lines
860 B
Bash

# Mock Mode Configuration for Pulse Development
# This file is local-only and not committed to the repository
# Enable/disable mock mode (true/false)
PULSE_MOCK_MODE=true
# Number of mock nodes to generate
PULSE_MOCK_NODES=7
# Number of VMs per node
PULSE_MOCK_VMS_PER_NODE=5
# Number of LXC containers per node
PULSE_MOCK_LXCS_PER_NODE=8
# Enable random metric changes over time (true/false)
PULSE_MOCK_RANDOM_METRICS=true
# Percentage of guests that should be stopped (0-100)
PULSE_MOCK_STOPPED_PERCENT=20
# Test different node count scenarios:
# - 1-4 nodes: Regular cards (already tested)
# - 5-9 nodes: Compact cards (default: 7)
# - 10+ nodes: Ultra-compact list
# Examples for different scenarios:
# Small setup: PULSE_MOCK_NODES=3
# Medium setup: PULSE_MOCK_NODES=7 (default)
# Large setup: PULSE_MOCK_NODES=15
# Huge setup: PULSE_MOCK_NODES=25