Health surfaces
Platform, tenant, provider, API, wallet, domain, SSL and runtime health can be represented independently.
- Platform health
- Provider health
- Wallet health
- SSL health
OPERATIONS & NOC
Operations visibility is designed around identifying what failed, where it failed and what the operator can do next.
DETAIL ↓NETXGEN / PUBLIC NETWORKMAINnetxgengaming.comTECHNICtechnic.netxgengaming.comSTATUSstatus.netxgengaming.com
07
Operations & NOC
Operations visibility is designed around identifying what failed, where it failed and what the operator can do next. The sections below describe the capability surface in customer-facing technical language while intentionally avoiding internal credentials, topology and commercially sensitive controls.
Technical logs
Central API, integration, migration, runtime, callback, authentication and database logs support diagnosis.
- API logs
- Provider errors
- Callback errors
- Database errors
Failure context
Structured error codes, subsystem identification, last-check timestamps, remediation hints and retry actions shorten diagnosis time.
- Failure reason
- Subsystem identification
- Suggested remediation
- Retry actions
Incident operations
Incident visibility, maintenance state, health history and operational notifications create a single operating picture.
- Incident management
- Maintenance visibility
- Health history
- Operational notifications