DDoS Sensor Detail
There is no standalone DDoS sensor page in the FluxBilling admin panel. Use the Activity Log for security visibility and your network provider for mitigation.
Overview
This article explains where security and network-attack visibility lives in your FluxBilling admin panel. There is no standalone DDoS sensor page in the panel today: you will not find a separate sensor view to open, sensor cards to click, or per-sensor tabs for traffic charts, protected address ranges, routing peers, or attack timelines. Security and audit visibility is handled through the tools described below, and network-level attack mitigation is provided at the network and data-center layer rather than from inside the billing panel.
Where security visibility lives
The admin panel does not include a dedicated DDoS Protection or DDoS Sensor page. If you are investigating an incident or want a record of what happened on your platform — suspicious sign-in attempts, configuration changes, and other security-relevant events — use the Activity Log.
- Open the Activity Log from the admin header. It sits next to Settings and uses a clipboard-style icon (it is available to administrators and staff with settings access).
- Review the chronological list of recorded actions. Each entry shows what happened, who performed it, and when.
- Use the search and filter controls to narrow the list to a specific user, action type, or date range while you investigate.
For a full walkthrough of filtering and interpreting entries, see the Activity Log article.
Protecting your infrastructure from attacks
Volumetric and network-layer attack mitigation — absorbing or filtering malicious traffic before it reaches your services — is normally delivered at the network edge and data-center layer, not from within the billing panel. To put protection in place:
- Coordinate filtering and traffic-scrubbing with your upstream network provider or the facility that hosts your hardware.
- Confirm what protection is included with your connectivity or rack agreement, and what thresholds trigger automatic mitigation.
- Keep contact and escalation details for your provider on hand so you can respond quickly during an active attack.
Note: Older documentation may have described a per-sensor management view with traffic graphs, protected address ranges, routing peers, flow-telemetry sources, attack lists, and reinstall or key-rotation actions. That view is not part of the current product. If you came here looking for it, use the Activity Log for after-the-fact visibility and your network provider for live mitigation.