Uptime checks, alerts, status reports and the status page
This page covers how you find out that something needs attention: scheduled uptime checks of your own endpoints, alert rules that notify a channel, periodic status-report e-mails, personal notification switches, and Noxtica’s public status page.
A workspace administrator sets up checks, channels, rules and reports in Backoffice. Anyone can read the public status page.
What it is
Availability depends on your plan, role and the modules enabled for your organisation.
| Surface | Where | What it is for |
|---|---|---|
| Uptime Checks | Backoffice → Web Analytics & Privacy → Uptime Checks | Scheduled HTTPS checks of endpoints you own, after you prove ownership |
| Alerts | Backoffice → Integrations & API → Alerts | Channels, rules, delivery history and a privilege-escalation view |
| Status Reports | Backoffice → Integrations & API → Status Reports | Periodic e-mail summaries of your workspace |
| Notifications | Backoffice → Settings → Notifications | Personal switches for e-mail and in-console notifications |
| Status page | status.noxtica.com | Public health of Noxtica services, incidents and planned maintenance |
Gates you may meet
- Alert channels can be created only for channel types that are switched on for your organisation. Until one is, the Alerts page says “Alert channels are not enabled for this platform yet”. You can still author rules; they start evaluating once alerting is switched on.
- Uptime probing is an optional capability. Without it, targets stay in the Probing or Disabled state.
- Status-report delivery depends on whether report sending is active for your organisation. Your choice on the page is recorded either way.
Alert limits
| Limit | Value |
|---|---|
| Channels per workspace | 10 |
| Rules per workspace | 20 |
| Channels a single rule can notify | 10 |
| Channel or rule name length in the editor | 80 characters |
| Consecutive failed deliveries before a channel pauses itself | 5 |
| Minimum re-notify interval while a rule keeps firing | 5 minutes (default 4 hours) |
An hourly dispatch cap also applies. Lower-severity alerts are dropped first when it is reached, and the History tab says so. Bounds can change; Backoffice shows the values in force.
Channel types
| Type | You provide |
|---|---|
| Webhook (Generic webhook) | An HTTPS endpoint URL. Noxtica signs each payload; verify the X-Noxtica-Signature header. |
| Webhook (PagerDuty) | A PagerDuty Integration Key (32 hex characters). No URL. |
| Webhook (Opsgenie) | An Opsgenie API key and a region (us or eu). No URL. |
| Slack | A Slack incoming-webhook URL |
| Microsoft Teams | A Teams workflow callback URL |
| Telegram | Your own bot token and a chat ID |
| A Send to address, a Send from address and a Resend API key |
Credentials are stored encrypted and never shown again after you save them. Noxtica does not manage on-call rosters, schedules or escalation policies; PagerDuty and Opsgenie decide routing behind your key.
The Privilege escalations tab on the Alerts page is not paging escalation. It is a read-only view of role changes, cross-tenant reads by platform staff and credit grants or revocations.
Prerequisites
- Administrator role. Creating, editing and deleting checks, channels, rules and report settings asks for a fresh step-up MFA confirmation.
- For uptime checks: a URL on a domain you own, and the ability to add a DNS TXT record or serve a file under
/.well-known/. - For alert channels: the account or key on the receiving side (Slack, Teams, Telegram, Email provider, PagerDuty, Opsgenie or your own endpoint).
- For status reports: a valid e-mail address if you want an external contact.
Steps
1. Add an uptime check
- Backoffice → Web Analytics & Privacy → Uptime Checks.
- Enter the Target URL. It must be HTTPS, without embedded credentials, and must not point at localhost or a private address.
- Enter an optional Label (up to 120 characters).
- Choose the Ownership proof method: DNS TXT record or .well-known HTTPS file.
- Press Add target.
Backoffice shows the challenge to publish. For the DNS TXT method, create a TXT record named _noxtica-uptime-challenge.<host> with the value shown. For the file method, serve the value as the response body at https://<host>/.well-known/noxtica-uptime-challenge. Use Copy challenge to copy it.
2. Verify ownership and enable the check
- Publish the challenge.
- Press Verify. A proof stays valid for 30 days; after that you verify again. Verification is limited to 5 attempts per minute for each target.
- Press Enable. A target needs a valid proof before it can be enabled.
A badge shows how many targets are enabled against your allowance (for example 2/5 enabled). A workspace can hold up to 25 targets. The allowance of enabled targets defaults to 5; Backoffice shows the value in force. Enabled targets are probed on a schedule of about every five minutes.
Each row shows a state: Probing, Up, Degraded, Down or Disabled. Changing a target’s URL to a different host clears its proof and disables it until you verify again.
3. Add an alert channel
- Backoffice → Integrations & API → Alerts → Channels → Add channel.
- Choose the Channel type. For Webhook, pick the Webhook template: Generic webhook, PagerDuty or Opsgenie.
- Enter a Channel name and the fields for the type (see the table above), then save.
- Press Send test. The test alert uses the same delivery path as a real alert. For PagerDuty, repeated tests collapse onto one incident.
A channel that fails 5 deliveries in a row pauses itself and shows an auto-paused notice. Fix the cause, then send a successful test to clear it.
4. Create an alert rule
- On the Alerts page open Rules. A rule needs at least one channel first.
- Press From template for a curated rule, or Add rule for the full editor.
- Name the rule, set the Threshold, Window and Severity (Info, Warning or Critical), and tick the channels under Notify these channels.
- Save. Each rule shows a state: OK, Pending or Firing.
The curated templates are: Quota usage threshold, High-risk traffic spike, Challenge failure rate, Tracker traffic volume, Honeypot tripwire rate, SEO score dropped below threshold and SEO issue count spiked.
The Add rule editor offers these metric templates: Quota usage, High-risk spike, Flag-hit volume, Traffic volume, Challenge failure rate, Tracker volume, Risk rule fire volume, APM p95 latency, APM error rate, APM throughput drop and APM service down. The template, and so the metric, cannot be changed after you create a rule. APM rules are scoped to one project, one environment and one service.
Daily metrics are evaluated on the last full day. The editor has no template for uptime or browser RUM metrics today.
5. Read alert history
Alerts → History. Each row shows the time, rule, channel, event (Firing, Resolved or Test), severity and status: Delivered, Queued, Failed, Channel paused or Dropped (cap). Credentials and URLs are never shown.
6. Turn status reports on or off
- Backoffice → Integrations & API → Status Reports.
- The switch Send periodic status reports to workspace admins is on by default. Turn it off to stop reports; your opt-out always wins over the default.
- Optionally enter a Nominated external contact (a further recipient outside your admin list) and a Display timezone (an IANA name such as
Europe/Paris; blank means UTC). - Save and confirm step-up MFA. Press Preview to render your next report with live data. Nothing is e-mailed.
Reports summarise your own workspace only: traffic, detection activity, usage and quota. Recipients are every active workspace administrator plus the nominated contact.
7. Set your personal notifications
Backoffice → Settings → Notifications. Three switches, all on by default: Critical device email (e-mail when a device exceeds the configured risk threshold), In-app alerts (notifications inside the console) and Weekly digest (a summary every Monday at 09:00 workspace time).
8. Follow the public status page
Open https://status.noxtica.com. It needs no sign-in.
- The banner shows the overall state: All Systems Operational, Degraded Performance, Partial / Major Outage or Some System Status Unknown.
- Each component shows a pill (Operational, Degraded, Down or Unknown) and a 90-day history strip. A table view of the same history is available under each strip.
- Components: Collector API, Backoffice / Dashboard, Website, Verify, Ingestion API and SIEM Event Delivery.
- Incidents and scheduled maintenance windows appear on the page.
- Subscribe to incidents (Atom) links to
https://status.noxtica.com/feed.xml. Add it to a feed reader to follow incidents.
The status page is informational. It is not a contractual service-level agreement. On your Backoffice Home page, a Platform status card shows the same summary for every signed-in role.
Verify it works
- A verified, enabled uptime target shows Up after the next probe.
- Send test shows a success message and a row with event Test and status Delivered in History. The message arrives on the receiving side (Slack message, PagerDuty incident, e-mail, signed request).
- A new rule shows OK. When its condition holds for its window it moves to Pending and then Firing, and History records a Firing row per channel.
- After you save the Status Reports switch, the page shows “Enabled (default)” or “Turned off for this workspace”.
https://status.noxtica.com/feed.xmlloads as an Atom document, empty when there are no incidents.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| “Alert channels are not enabled for this platform yet” | No channel type is switched on for your organisation | Ask your account team. |
| “Alert evaluation is not turned on for this platform yet” | Alerting is not switched on | You can author rules now; they evaluate after your organisation is enabled. |
| “You have reached the limit of 10 channels” or “of 20 rules” | Workspace limit | Delete one you no longer use. |
| “Enter a valid https:// URL. Localhost and private addresses are not allowed.” | Webhook or uptime URL is not public HTTPS | Use a public HTTPS URL. |
| “Enter a valid Slack incoming-webhook URL” | The URL is not on hooks.slack.com | Copy the incoming-webhook URL from Slack. |
| Channel shows auto-paused | 5 consecutive failed deliveries | Fix the endpoint or credential, then send a successful test. |
| Test fails (“Could not send the test alert”) | Wrong credential, blocked endpoint or provider error | Check the credential and the receiving service. |
| History shows “Dropped (cap)” | The hourly dispatch cap was reached | Reduce noisy rules; lower-severity alerts are dropped first. |
| Rule editor needs a channel | A rule must notify at least one channel | Add a channel first. |
| Uptime: “Ownership check failed ()” | The record or file is missing or differs | Publish the exact value shown and press Verify again. The reason is one of proof_mismatch, dns_lookup_failed, unreachable, ssrf_blocked, overflow or unexpected_status. |
Uptime: enabling fails and the message names ownership_unverified or ownership_expired | No proof, or the 30-day proof lapsed | Verify again, then Enable. |
Uptime: enabling fails and the message names uptime_quota_exhausted | The enabled-target allowance is used | Disable another target, or ask your account team. |
| Uptime: adding fails with “That URL is already registered as an uptime target” | Duplicate URL | Edit the existing target. |
| Status Reports: “Report delivery is not active yet” | Sending is not active for your organisation | Your choice is recorded and applies once sending is active. |
| Status Reports: “Enter a valid email address” or “Enter an IANA timezone name” | Invalid contact or timezone | Correct the value or leave it blank. |
| Status page shows Ingestion API as Degraded | The status probe expects the health endpoint to answer, and an unauthenticated request to the trace route to answer 401 | Check the status page incident list. Contact support if it persists. |
| Privilege escalations tab says “Not armed” | The source is off by default | Ask your account team. |
Related
- APM and the ingestion service (OTLP) for the APM metrics used by APM alert rules.
- SEO tools: page checks, site crawls and search score for the SEO score used by SEO alert templates.
- Event sinks (SIEM export) to forward events to your security tooling.
- Integrations and API pages for the other Integrations & API pages.
- Sign-in, SSO, SCIM, MFA and IP allowlist for step-up MFA.
- Security for how the status page relates to service commitments.