Observability & Error Tracking

Visible Error Influx

Hypertask provides a public error-influx endpoint at https://hypertask.app/errors where application errors, including those during AI-chat interactions, are reported and processed. The endpoint surfaces:

• Error details (stack traces, context)
• Auto-filed tickets via the existing MCP task service
• Deduplication and rate limiting for stability

Tip

Accessed from the URL or through integrations; no auth token is required for ingestion.

PostHog Analytics Proxy

Hypertask routes analytics through the first-party domain e.hypertask.ai. Client-side tracking sends requests to the proxy instead of directly to PostHog servers.

Effects:

• Zero requests to posthog.com reach the browser
• Proxy handles CORS preflight, asset loads, and feature flags
• Analytics capture returns Ok on all tracked events

This ensures合规 cookie consent across all consent platforms by keeping analytics under your own domain.

Web Performance Telemetry

Hypertask tracks real-world user performance through PostHog Core Web Vitals—First Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift, and Time to Interactive—to understand how fast the app feels.

Note

This data is logged anonymously via PostHog EU and never tied to your projects or tasks. Metrics reflect aggregate app performance for all users.

Self-Healing Error Pipeline

When production or client-side errors occur in Hypertask, the self-healing error pipeline automatically catches, dedupes, and:

• Files bug tickets to a dedicated board or project
• Sends telemetry via PostHog EU
• Reports through /api/errors for downstream processing

The pipeline operates on both server and browser-level catchers, ensuring coverage of:

• Server crashes and backend errors
• Client-side exceptions (especially during AI-chat interactions)
• Application errors originating from external integrations

Caution

The exposed /api/errors endpoint respects a server-side allowlist. Public access is restricted to whitelisted requests; rate-capping prevents abuse.

Using Error Telemetry

The error influx endpoint is monitored proactively. Sentinel agents review new entries and triage tickets automatically.

• From Sentry / log shipping: If you ship errors to Sentry, Datadog, or similar, forward error JSON to https://hypertask.app/errors with the same field shape and the system will match against existing tickets for deduplication.
• From application logs: For custom logging integrations, POST JSON with consistent keys such as message, stackTrace, context, userAgent, projectId.

FAQ

Can I disable the self-healing behavior?

The error pipeline respects privacy and tenant scopes; errors that fall outside your boardâ\x80\x99s context are not auto-filed. You can also route enterprise environments through custom observability stacks with appropriate rate-limiting.

Does this replace my existing error tracking?

Hypertask complements external tools. If you already monitor app health via Sentry/Datadog, use the influx endpoint to centralize onboarding and auto-file tickets while preserving your historical data.