The only tool you need to know what is happening and how to fix it.
Go alertingexception-trackerissue-trackinglogsmetricsmonitoringobservability-platformopen-telemetryotelsession-replaytelemetrytraces
Website pre image done
dduxe257b298a9d1
diff --git a/website/app/layout.tsx b/website/app/layout.tsxindex 63a3ae2f..dc481ab8 100644--- a/website/app/layout.tsx+++ b/website/app/layout.tsx@@ -27,7 +27,7 @@ export const metadata: Metadata = {alternates: {canonical: "./",},- title: "Traceway — Logs, Traces, Metrics, Session Replay, Stack Traces",+ title: "Traceway — Logs, Traces, Metrics, Session Replay, Exceptions",description:"Traceway is open-source observability for modern backends. Logs, traces, metrics, session replay, and stack traces — correlated by one trace ID. Self-host free or run on Traceway Cloud.",icons: {diff --git a/website/app/page.tsx b/website/app/page.tsxindex 7ca99576..5b04f9f5 100644--- a/website/app/page.tsx+++ b/website/app/page.tsx@@ -91,8 +91,8 @@ export default function Home() {/><PillarCardicon={Bug}- title="Stack traces"- description="Grouped, ranked, Impact Score."+ title="Exceptions / Stack Traces"+ description="Grouped, normalized, paired with replay."href="/product/stack-traces"color="a3"/>diff --git a/website/app/product/metrics/page.tsx b/website/app/product/metrics/page.tsxindex ae8e0e37..fab68b6e 100644--- a/website/app/product/metrics/page.tsx+++ b/website/app/product/metrics/page.tsx@@ -1,23 +1,12 @@import Link from "next/link";-import {- ArrowRight,- BarChart3,- Cpu,- LayoutDashboard,- Network,- Package,- Radio,- Ruler,-} from "lucide-react";+import { ArrowRight, BarChart3 } from "lucide-react";import { Chip } from "@/components/chip";import { SectionHead } from "@/components/section-head";import { FeatureRow } from "@/components/feature-row";-import { BentoGrid, BentoCell } from "@/components/bento-grid";import { FaqList } from "@/components/faq-list";import { FinalCTA } from "@/components/final-cta";import { AuroraBackground } from "@/components/aurora-background";-import { Terminal } from "@/components/terminal";export default function MetricsPage() {return (@@ -33,9 +22,9 @@ export default function MetricsPage() {Measure what matters, <em>without the bill shock.</em></h1><p className="hero-sub">- Custom application metrics, automatic server metrics, flexible- widget dashboards, and OpenTelemetry ingestion — all included in- every plan. No per-metric billing, no surprise overages.+ Application metrics via OpenTelemetry, automatic server metrics,+ and flexible widget dashboards — all included, with no per-metric+ billing and no surprise overages.</p><div className="hero-cta-row"><Link href="https://docs.tracewayapp.com" className="btn btn-accent">@@ -54,38 +43,20 @@ export default function MetricsPage() {eyebrow="Application metrics"title={<>- Custom metrics with <em>one function call</em>+ Application metrics <em>via OpenTelemetry</em></>}- description="Counter, Gauge, and Histogram types with dimensional tags. Emit metrics from anywhere in your code — the SDK batches, compresses, and ships them to Traceway without blocking your hot path."+ description="Emit Counter, Gauge, and Histogram metrics through the OpenTelemetry SDK you already have. Traceway ingests OTLP natively, preserves units and dimensional tags, and bills nothing per metric."bullets={[- "Counter / Gauge / Histogram types",- "Dimensional tags for facet breakdowns",- "Single-call SDK API",- "Zero impact on request latency",+ "OTLP/HTTP and OTLP/gRPC ingestion",+ "Counter / Gauge / Histogram preserved natively",+ "Dimensional tags become facet filters",+ "No per-metric billing",]}- image={{ src: "/images/screenshot-4.png", alt: "Custom metrics dashboard" }}+ image={{ src: "/images/screenshot-4.png", alt: "Application metrics dashboard" }}/></section>- {/* Code example */}- <section className="wrap py-16">- <div className="max-w-3xl mx-auto">- <Terminal- title="capture custom metrics"- lines={[- { type: "mute", content: "// Track business metrics alongside system metrics" },- { type: "cmd", content: 'traceway.Metric.Counter("signups", 1, tags)' },- { type: "cmd", content: 'traceway.Metric.Gauge("queue.depth", 42, tags)' },- { type: "cmd", content: 'traceway.Metric.Histogram("checkout.ms", 312, tags)' },- { type: "mute", content: "// Tags can be plan, region, tenant — anything you want to slice by" },- { type: "ok", content: '✓ metrics indexed by type, tag, and time — query anywhere' },- ]}- showCursor- />- </div>- </section>-{/* Server metrics */}<section className="wrap"><FeatureRow@@ -124,66 +95,6 @@ export default function MetricsPage() {/></section>- {/* Ingest bento */}- <section className="wrap py-10">- <SectionHead- eyebrow="Ingest"- title={- <>- OpenTelemetry metrics — <em>first-class</em>- </>- }- description="Bring metrics from anywhere. Traceway speaks OTLP natively and registers every metric with type, unit, and cardinality."- />- <BentoGrid>- <BentoCell- size="wide"- icon={Network}- title="OTLP/HTTP + OTLP/gRPC"- iconColor="var(--a2)"- >- <p>- Point any OpenTelemetry SDK at Traceway. Sum, Gauge, and- Histogram metric types are all understood natively — no- translation layer, no metric-name mangling.- </p>- </BentoCell>- <BentoCell- size="med"- icon={Package}- title="Metric Registry"- iconColor="var(--a1)"- >- <p>- Every metric shows up with its type, unit, description,- last-seen timestamp, and cardinality. Spot runaway tag explosions- before they hit your bill.- </p>- </BentoCell>- <BentoCell- size="med"- icon={Radio}- title="Prometheus scrape"- iconColor="var(--ok)"- >- <p>- Traceway can pull <code>/metrics</code> endpoints on a- configurable interval. Your existing Prometheus exporters work- unchanged.- </p>- </BentoCell>- <BentoCell size="sm" icon={Cpu} title="StatsD compat">- <p>UDP ingestion for legacy StatsD metric streams.</p>- </BentoCell>- <BentoCell size="sm" icon={Ruler} title="Custom units">- <p>Bytes, seconds, percentages — declare once, render consistently.</p>- </BentoCell>- <BentoCell size="sm" icon={LayoutDashboard} title="Always in context">- <p>Metrics link back to the traces, logs, and issues around them.</p>- </BentoCell>- </BentoGrid>- </section>-<FinalCTAtitle={<>@@ -208,18 +119,20 @@ export default function MetricsPage() {<FaqListitems={[{- q: "How do I emit a custom metric?",+ q: "How do I emit an application metric?",a: (<><p>- With the Traceway SDK, a single call:{" "}- <code>traceway.Metric.Counter("signups", 1, tags)</code>- {" "}— that's it. Full docs cover Gauge and Histogram.+ Point any OpenTelemetry SDK at{" "}+ <code>/api/otel/v1/metrics</code> — OTLP/HTTP and+ OTLP/gRPC are both supported natively. Counter, Gauge,+ and Histogram metric types are ingested as-is, and+ dimensional tags become facet filters in the dashboard.</p><p>- Or send metrics via OpenTelemetry at{" "}- <code>/api/otel/v1/metrics</code> — OTLP/HTTP and- OTLP/gRPC are both supported natively.+ If you're instrumenting from scratch, the+ OpenTelemetry metrics SDK is the recommended path for+ every language we support.</p></>),@@ -236,10 +149,6 @@ export default function MetricsPage() {q: "Can I query metrics by tag or dimension?",a: "Yes. Every tag becomes a facet you can filter on; widget groups let you build per-dimension chart panels. For example, a `plan` tag on a signups metric lets you chart signups broken down by plan, region, or tenant.",},- {- q: "Does Traceway support Prometheus?",- a: "Yes. Traceway can scrape /metrics endpoints on a configurable interval. Your existing Prometheus exporters work unchanged — just point Traceway at their address and choose a scrape interval.",- },]}/></div>diff --git a/website/app/product/performance/page.tsx b/website/app/product/performance/page.tsxindex b88e0311..ceeca884 100644--- a/website/app/product/performance/page.tsx+++ b/website/app/product/performance/page.tsx@@ -7,6 +7,7 @@ import { FeatureRow } from "@/components/feature-row";import { FaqList } from "@/components/faq-list";import { FinalCTA } from "@/components/final-cta";import { AuroraBackground } from "@/components/aurora-background";+import { ImpactScoreVisual } from "@/components/impact-score-visual";export default function PerformancePage() {return (@@ -36,6 +37,22 @@ export default function PerformancePage() {</div></section>+ {/* Impact Score — scoring and ranking logic */}+ <section className="wrap py-20">+ <SectionHead+ eyebrow="Impact Score"+ title={+ <>+ One score. Five signals. <em>Zero guesswork.</em>+ </>+ }+ description="The Impact Score combines five service-level indicators into one automatic priority for every endpoint. It takes the max across all five — if any single signal is bad, the endpoint surfaces immediately."+ />+ <div className="mt-10 max-w-4xl mx-auto">+ <ImpactScoreVisual />+ </div>+ </section>+{/* Drill into any request — absorbed from home */}<section className="wrap"><FeatureRow@@ -181,6 +198,33 @@ export default function PerformancePage() {<div className="mt-4"><FaqListitems={[+ {+ q: "What is the Impact Score?",+ a: (+ <>+ <p>+ The Impact Score is Traceway's automatic prioritization+ system. It combines five service-level indicators — an+ inverted apdex variant, error rate floor, P99 latency+ floor, client error floor, and volume error floor — into+ a single 0-100 score for every endpoint.+ </p>+ <p>+ It takes the max across all five, so if any single+ signal is degraded that endpoint surfaces immediately.+ You can adjust the slow endpoint threshold per endpoint+ to tune the apdex calculation for routes with different+ latency profiles.+ </p>+ <p>+ For incident management, notification rules fire when+ the Impact Score or error rate crosses a threshold, and+ route alerts to Slack, GitHub Issues, email, or custom+ webhooks.+ </p>+ </>+ ),+ },{q: "What percentiles does Traceway track?",a: "Traceway calculates P50 (median), P95, and P99 latency percentiles for every endpoint. This gives you a clear picture of both typical and worst-case response times for your application.",diff --git a/website/app/product/stack-traces/page.tsx b/website/app/product/stack-traces/page.tsxindex 0b2c4868..9a15c371 100644--- a/website/app/product/stack-traces/page.tsx+++ b/website/app/product/stack-traces/page.tsx@@ -1,27 +1,12 @@-import Image from "next/image";import Link from "next/link";-import { ArrowRight, Bug, Layers, Globe, TrendingUp } from "lucide-react";+import { ArrowRight, Bug } from "lucide-react";import { Chip } from "@/components/chip";-import { Eyebrow } from "@/components/eyebrow";import { SectionHead } from "@/components/section-head";import { FeatureRow } from "@/components/feature-row";import { FaqList } from "@/components/faq-list";import { FinalCTA } from "@/components/final-cta";import { AuroraBackground } from "@/components/aurora-background";-import { ImpactScoreVisual } from "@/components/impact-score-visual";--const frameworks = [- { name: "Gin", src: "/images/frameworks/gin.png" },- { name: "Chi", src: "/images/frameworks/chi.png" },- { name: "Express", src: "/images/frameworks/express.png" },- { name: "NestJS", src: "/images/frameworks/nestjs.png" },- { name: "Next.js", src: "/images/frameworks/nextjs.png" },- { name: "Svelte", src: "/images/frameworks/svelte.png" },- { name: "Remix", src: "/images/frameworks/remix.png" },- { name: "OpenTelemetry", src: "/images/frameworks/otel.png" },- { name: "Cloudflare", src: "/images/frameworks/cloudflare.png" },-];export default function StackTracesPage() {return (@@ -32,16 +17,15 @@ export default function StackTracesPage() {<div className="wrap relative z-10"><Chip variant="crit"><Bug className="h-3 w-3 inline mr-1" />- Stack Traces+ Exceptions / Stack Traces</Chip><h1 className="mt-6">Find and fix issues <em>before your users notice.</em></h1><p className="hero-sub">- Every exception, grouped and ranked by automatic Impact Score.- Traceway normalizes stack traces with a 10-step pipeline and- SHA-256 hashes them — thousands of duplicates collapse into one- ranked issue.+ Every exception, grouped by a 10-step normalization pipeline and+ SHA-256 hash — thousands of duplicates collapse into one issue,+ paired with the session replay or screen recording that caused it.</p><div className="hero-cta-row"><Link href="https://docs.tracewayapp.com" className="btn btn-accent">@@ -54,22 +38,6 @@ export default function StackTracesPage() {</div></section>- {/* Impact Score section */}- <section className="wrap py-20">- <SectionHead- eyebrow="Impact Score"- title={- <>- One score. Five signals. <em>Zero guesswork.</em>- </>- }- description="The Impact Score combines five service-level indicators into one automatic priority for every endpoint. It takes the max across all five — if any single signal is bad, the endpoint surfaces immediately."- />- <div className="mt-10 max-w-4xl mx-auto">- <ImpactScoreVisual />- </div>- </section>-{/* Every exception grouped and ranked — absorbed from home */}<section className="wrap"><FeatureRow@@ -125,39 +93,25 @@ export default function StackTracesPage() {/></section>- {/* Framework showcase */}- <section className="wrap py-20 text-center">- <div className="max-w-3xl mx-auto flex flex-col items-center gap-5">- <div- className="w-12 h-12 rounded-[10px] flex items-center justify-center"- style={{- background: "color-mix(in oklab, var(--a4) 18%, transparent)",- border: "1px solid color-mix(in oklab, var(--a4) 40%, transparent)",- color: "var(--a4)",- }}- >- <Globe className="w-5 h-5" />- </div>- <Eyebrow>Full stack</Eyebrow>- <h2>Track issues across your full stack</h2>- <p style={{ color: "var(--fg-1)", fontSize: 17 }}>- From Go backends to JavaScript frontends, Traceway captures- exceptions everywhere your code runs. Unified view of issues across- services, with full stack traces and contextual tags.- </p>- <div className="flex flex-wrap items-center justify-center gap-8 md:gap-10 pt-6 opacity-80">- {frameworks.map((fw) => (- <Image- key={fw.name}- src={fw.src}- alt={fw.name}- width={40}- height={40}- className="h-8 w-auto opacity-80 hover:opacity-100 transition-all"- />- ))}- </div>- </div>+ {/* Visual context — pair stack traces with session replay */}+ <section className="wrap">+ <FeatureRow+ reverse+ eyebrow="Visual context"+ title={+ <>+ Pair every stack trace with the <em>replay that caused it</em>+ </>+ }+ description="When a backend exception fires, Traceway attaches the session replay or mobile recording the user was generating at that moment. Open the stack trace — the replay is right there. See what the user did, what the UI looked like, and where the code blew up, in one pane."+ bullets={[+ "Web DOM replay linked by trace ID",+ "Flutter and React Native screen recording",+ "Jump from stack frame → exact frame of the replay",+ "Frontend + backend context in one pane",+ ]}+ image={{ src: "/images/screenshot-2.png", alt: "Stack trace paired with session replay" }}+ /></section><FinalCTA@@ -180,33 +134,6 @@ export default function StackTracesPage() {<div className="mt-4"><FaqListitems={[- {- q: "What is the Impact Score?",- a: (- <>- <p>- The Impact Score is Traceway's automatic prioritization- system. It combines five service-level indicators — an- inverted apdex variant, error rate floor, P99 latency- floor, client error floor, and volume error floor — into- a single 0-100 score for every endpoint.- </p>- <p>- It takes the max across all five, so if any single- signal is degraded that endpoint surfaces immediately.- You can adjust the slow endpoint threshold per endpoint- to tune the apdex calculation for routes with different- latency profiles.- </p>- <p>- For incident management, notification rules fire when- the Impact Score or error rate crosses a threshold, and- route alerts to Slack, GitHub Issues, email, or custom- webhooks.- </p>- </>- ),- },{q: "How does error grouping work?",a: "Traceway applies a 10-step normalization pipeline to every stack trace: extracting the error type, removing absolute file paths, replacing hex addresses, UUIDs, IPs, timestamps, and numeric IDs with placeholders, normalizing whitespace, and stripping ANSI codes. The result is hashed with SHA-256 so identical logical errors always group together, even if runtime values differ.",@@ -220,8 +147,8 @@ export default function StackTracesPage() {a: "Traceway normalizes stack traces by removing runtime-specific values like memory addresses, file paths, UUIDs, and timestamps before hashing. This means the same bug produces the same group regardless of which server or environment it occurred on.",},{- q: "Can I track frontend JavaScript errors?",- a: "Yes. Traceway supports frontend frameworks like Next.js, Svelte, and Remix alongside backend frameworks like Express and NestJS. Errors from both your frontend and backend appear in the same dashboard with full stack traces. Source maps upload resolves minified traces back to your original source.",+ q: "Can I track frontend and mobile errors alongside the backend?",+ a: "Yes. Web (Next.js, Svelte, Remix) and mobile (Flutter, React Native) exceptions land in the same dashboard as your backend ones, and each one carries the session replay or screen recording the user was generating when it fired. Open the stack trace and the exact frame of the replay is one click away. Source maps resolve minified web traces back to original source.",},]}/>diff --git a/website/components/site-footer.tsx b/website/components/site-footer.tsxindex 20c59d67..c304cf74 100644--- a/website/components/site-footer.tsx+++ b/website/components/site-footer.tsx@@ -15,7 +15,7 @@ const COLUMNS: Column[] = [{ label: "Traces", href: "/product/traces" },{ label: "Metrics", href: "/product/metrics" },{ label: "Session Replay", href: "/product/session-replay" },- { label: "Stack Traces", href: "/product/stack-traces" },+ { label: "Exceptions / Stack Traces", href: "/product/stack-traces" },],},{diff --git a/website/components/site-header.tsx b/website/components/site-header.tsxindex 6aa9da87..03c5de58 100644--- a/website/components/site-header.tsx+++ b/website/components/site-header.tsx@@ -51,8 +51,8 @@ const PILLARS: NavItem[] = [icon: Video,},{- title: "Stack Traces",- description: "Grouped and ranked by automatic Impact Score.",+ title: "Exceptions / Stack Traces",+ description: "Grouped, normalized, and paired with the replay that caused them.",href: "/product/stack-traces",icon: Bug,},