Creytix Error Tracking

Overview

Creytix Error Tracking catches the exceptions your site throws in production — the stack traces, the failed requests, the errors a visitor hits but never reports — and puts them in front of your team before they pile up. It runs on a self-hosted, Sentry-compatible path, so the same error-reporting protocol your team may already know works here too, without a seat-based SaaS bill behind it.

Because error capture is wired at the workspace level, errors from a site you manage in Creytix land in the same place as everything else you're tracking for it.

How it works

Error Tracking follows the standard error-reporting flow:

1. Instrument — your site sends error events using a widely-supported error-reporting SDK, the same one many teams already use.
2. Ingest — events land on Creytix's own error-tracking service instead of a third-party SaaS endpoint.
3. Triage — errors group by type and frequency in the operator dashboard, so your team can see what's actually breaking and how often.

Steps

1. •

   Confirm Error Tracking is wired

   From the Creytix Control Panel, open your workspace and select Error Tracking under Connect. Live sites ship with capture configured as part of setup.

2. •

   Let errors report in

   Once wired, uncaught exceptions and failed requests report automatically — there's nothing more to instrument for standard errors.

3. •

   Triage in the dashboard

   Review grouped errors by frequency and recency, and see which ones are new since your last check.

4. •

   Resolve and track

   Mark issues resolved as your team fixes them, so the dashboard reflects what's actually still open.

Capabilities

• Fleet-wide capture — error events from sites you manage in Creytix land on infrastructure you control.
• Self-hosted, Sentry-compatible path — uses a widely-supported error-reporting protocol, not a proprietary one.
• Grouped triage view — errors roll up by type and frequency instead of arriving as an unsorted stream.
• Workspace-scoped — errors are visible alongside the site they came from, in the same Control Panel as the rest of Connect.

Limits & honest scope

Creytix Error Tracking is built to catch and surface errors for teams already running their site in Creytix — not to be a full observability or APM platform.

• There's no distributed tracing or performance-monitoring layer yet — this is error capture, not end-to-end request tracing.
• Alerting integrations (paging, on-call routing) are still growing; check the tier badge and the changelog for what's live.
• Source-map–deobfuscated stack traces depend on your build wiring things up correctly — Creytix doesn't magically unminify code it was never given.

We would rather tell you what Error Tracking doesn't do yet than have you find a blind spot in production.

Related

• Creytix Connect overview
• Creytix Status
• What Creytix replaces