Debug visibility built for evidence, not guesswork.

Advanced Subscriber Intelligence is built for real operational environments, and real operational environments occasionally get strange. The ASI Debug & Diagnostics System exists to make those moments less blind, less frustrating, and far more explainable. Instead of leaving operators to poke around in the dark, ASI gives them toggles, logs, filtered views, raw file access, environment context, and support-bundle tools that help turn symptoms into evidence.

This is not decorative debugging. It is an operational layer built to help you see what changed, what the platform is doing, what the logs say, what can be bundled safely, and what should happen next. When a serious system misbehaves, visibility is not a luxury. It is oxygen.

🔎 Faster diagnosis

Debug visibility helps operators understand what is happening without building theories out of thin air.

📜 Better operational evidence

Logs, filtered views, raw file access, and environment context make troubleshooting more grounded and a lot less theatrical.

🛠️ Safer platform management

A stronger diagnostics layer helps operators act with more confidence when something needs review, support, or recovery.

⚙️ Debug Modes & Toggles

Enable debugging, SQL debug logging, and PHP error logging deliberately when investigation is needed instead of leaving the whole platform to whisper its problems in private.

📜 Log Viewing

Review filtered log tails for SQL export activity, PHP errors, Exim send context, and support-bundle audit events without modifying the underlying files.

📂 Raw File Access

Open raw log files directly when filtered views are not enough and the full picture matters.

🧾 Support Bundle Generator

Generate a local diagnostic package with system snapshot, selected log tails, and operator notes so support and troubleshooting start with evidence instead of a shrug.

🔒 Privacy Redaction

Redact sensitive data such as emails, IPs, and full URLs so diagnostics stay useful without becoming reckless.

🕵️ Audit Trail for Support Actions

Bundle previews and related support actions are audit-logged so investigation work leaves its own footprint instead of vanishing into fog.

📬 Sending Context

Tie diagnostics back into sending, queue control, delivery behaviour, and Exim-aware visibility when operational review is needed.

🌐 Environment Awareness

System snapshots and operating context help explain not just what happened, but the environment it happened in.

🤝 Remote Support Consent

Support starts only with visible and revocable client consent. Sessions are designed to be deliberately authorised, time-limited, and fully logged, with a clear kill switch so the client stays in control throughout.

🔐 Approval Handshake

The support handshake is designed to be deliberate and one-time, so remote access behaves like a specific approved event rather than some vague open door everyone forgets to shut later.

⏱️ Session Window Control

Once approved, support sessions remain tightly time-scoped. That means access is not just consented to, but deliberately bounded so support stays controlled, reviewable, and easy to end.

🛠️ Optional Remote Maintenance Permissions

During an active session, the client can optionally allow tightly scoped ASI-only maintenance actions such as clearing ASI-related log files or adjusting ASI debug flags. These requests stay controlled, auditable, and deliberately limited. Nothing here grants full admin access.

🛠️ For real troubleshooting moments

Whether something is stuck in the queue, a report looks odd, a setting is misbehaving, or an operator simply needs to understand what changed, the diagnostics system exists to make investigation faster and less chaotic. That kind of visibility matters more as the platform grows in capability and consequence.

📜 For calmer decisions and cleaner support

A good diagnostics layer lowers the emotional temperature of troubleshooting. Instead of reacting to symptoms alone, operators can review logs, settings, environment context, and support bundles with more confidence. That leads to calmer decisions, faster recovery, and a lot less keyboard archaeology.

For people who need to understand what the platform is doing when something feels off instead of treating every issue like a séance.

For teams supporting client environments where investigation needs to be evidence-led, calmer, and easier to hand over.

For people who need clearer visibility into sending behaviour, queue state, and operational anomalies before they become fires.

For anyone responsible for reviewing logs, tracing platform behaviour, and understanding the wider context behind a problem.