Auto-Flux (automatic right-sizing)

The Network section (branded “Flux” in some places) is for admins and needs the Network add-on on your plan. Depending on your plan and role you may not see it in the sidebar. If you think it should be part of your plan, ask your provider.

/network/auto-flux is a fleet view of every circuit with Auto-Flux turned on, showing its current state, recent peak utilization, and last automatic decision. Turn it on per circuit to let Vigilis raise or lower bandwidth from measured usage. It compares the higher of inbound and outbound utilization against the thresholds you set.

The defaults below are the recommended starting point. Change them only when you have a reason to.

Scale up

• Threshold: default 80% (range 1 to 99). When utilization crosses this, Auto-Flux raises bandwidth.
• Cooldown: default 30 minutes (range 1 to 1440). It will not scale up again until the cooldown passes.
• Ceiling: an optional cap, entered as ladder steps above current. Leave it blank to allow increases up to the platform maximum.

Scale down

• Threshold: default 20% (range 0 to 98). When utilization stays below this, Auto-Flux lowers bandwidth.
• Cooldown: default 60 minutes.
• Floor: an optional lower bound, entered as ladder steps below current.
• Anti-oscillation multiplier: default 2 (range 1 to 10). After any scale-up, it holds off a scale-down for the scale-down cooldown times this multiplier (60 minutes at the defaults), so bandwidth does not bounce.

Hysteresis (required hits)

Auto-Flux waits for required hits, default 3 (range 1 to 60), within a sample window, default 5 minutes (range 1 to 120). The newest reading must cross the threshold, and at least the required number of readings in the window must cross it too. A single brief spike does nothing.

Rate limiting and safety

Your carrier caps bandwidth changes at 24 per rolling 24 hours per circuit. As Auto-Flux approaches that limit, it protects the circuit in two stages:

• Near the limit, it reverts once to your standard bandwidth and emails your network contact.
• Just below the limit, it stops all automatic scaling (and blocks manual change) to reserve the last change as a buffer, so the circuit never gets stuck at the hard cap.

If you leave standard bandwidth blank, the auto-revert is off. Each change steps one rung on the circuit’s speed ladder, and Auto-Flux never exceeds the platform maximum.

Stale data

If the newest reading is older than twice the sample window (about 10 minutes at the defaults), Auto-Flux holds and does not scale until fresh data arrives.

Try a dry-run first

Dry-Run runs the exact decision against current data without making a change, and shows what it would have done. Use it before you turn the master toggle on.

Related

• Connecting usage data for where the utilization data Auto-Flux reads comes from.
• Bandwidth schedules if you would rather change bandwidth on the clock, or pause Auto-Flux after hours.
• Circuit connections for manual changes and the Activity log.