0Pricing
Next.js 15 Fullstack (App Router + Server Actions) · Ders

Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama

İşlem hatalarını ve performans ölçümlerini kullanıcı bağlamıyla birlikte gözlemlenebilirlik arka ucuna bildirin.

Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama, CoddyKit'te ücretsiz bir Next.js 15 Fullstack (App Router + Server Actions) dersidir. Bu, 4 dersinin 4. dersidir. Aşağıdan dersin tamamını ücretsiz okuyabilir, sonra tarayıcıda yerleşik kod editörü ve 7/24 yapay zeka koçu ile uygulamalı olarak pratik yapabilirsin. Bu, Next.js 15 Fullstack (App Router + Server Actions) öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. Next.js 15 Fullstack (App Router + Server Actions) kursu toplamda 4 dersten oluşur.

Bu dersin bazı bölümleri henüz çevrilmemiş olup İngilizce olarak gösterilmektedir.

Why Server Action Failures Need Special Treatment

Server Actions in Next.js 15 run on the server, outside the browser's error boundary. When a Server Action throws, the client receives a generic error — no stack trace, no context, no telemetry.

This means standard try/catch in the action is necessary but not sufficient. You also need to:

  • Capture the error with full server-side context (user ID, action name, request metadata)
  • Forward structured telemetry to an observability backend (e.g. OpenTelemetry, Sentry, Datadog)
  • Return a safe, serialisable error payload to the client — never expose raw stack traces

In this lesson you will build a complete, production-grade error-and-metrics pipeline around Server Actions.

Structuring a Safe Action Result Type

Before adding telemetry, agree on the shape every Server Action returns. A discriminated union makes error handling exhaustive on the client and prevents accidental data leaks.

Define this once in a shared types file and import it everywhere:

// lib/action-result.ts
export type ActionSuccess<T> = {
  ok: true;
  data: T;
  durationMs: number;
};

export type ActionFailure = {
  ok: false;
  code: string;       // machine-readable, e.g. 'VALIDATION_ERROR'
  message: string;    // human-readable, safe to show
  durationMs: number;
};

export type ActionResult<T> = ActionSuccess<T> | ActionFailure;

// Helper constructors
export function ok<T>(data: T, durationMs: number): ActionSuccess<T> {
  return { ok: true, data, durationMs };
}

export function fail(code: string, message: string, durationMs: number): ActionFailure {
  return { ok: false, code, message, durationMs };
}

Instrumenting Duration at the Action Level

Performance metrics begin with measuring how long each action takes. Wrap every action body with a performance.now() call so duration is always available for telemetry — even when the action fails.

The pattern below ensures durationMs is captured in both success and error paths:

// app/actions/create-post.ts
'use server';

import { ok, fail, type ActionResult } from '@/lib/action-result';
import { db } from '@/lib/db';

export async function createPost(
  _prev: ActionResult<{ id: string }> | null,
  formData: FormData
): Promise<ActionResult<{ id: string }>> {
  const start = performance.now();

  try {
    const title = formData.get('title') as string;
    if (!title?.trim()) {
      return fail('VALIDATION_ERROR', 'Title is required', performance.now() - start);
    }

    const post = await db.post.create({ data: { title } });
    return ok({ id: post.id }, performance.now() - start);
  } catch (err) {
    return fail('INTERNAL_ERROR', 'Failed to create post', performance.now() - start);
  }
}

Capturing User Context in Server Actions

Observability is only useful when you know who experienced an error. Server Actions have access to the same server context as Route Handlers, so you can read the session before running business logic.

Use Next-Auth (or any session library) to attach user context to every telemetry event:

// lib/auth-context.ts
import { auth } from '@/auth';   // next-auth v5

export type UserContext = {
  userId: string | null;
  email:  string | null;
  role:   string | null;
};

export async function getUserContext(): Promise<UserContext> {
  const session = await auth();
  return {
    userId: session?.user?.id   ?? null,
    email:  session?.user?.email ?? null,
    role:   (session?.user as { role?: string })?.role ?? null,
  };
}

Building a Telemetry Reporter

Centralise all telemetry calls in a single reporter module. This keeps observability logic out of business code and makes it easy to swap providers (Sentry, Datadog, OpenTelemetry) without touching action files.

The reporter records:

  • Errors — with user context, action name, and serialised error
  • Metrics — action name, outcome, and duration for latency percentiles
// lib/telemetry.ts
import type { UserContext } from './auth-context';

export type TelemetryEvent = {
  action:    string;
  ok:        boolean;
  durationMs: number;
  code?:     string;
  userId?:   string | null;
  email?:    string | null;
};

export async function reportEvent(event: TelemetryEvent): Promise<void> {
  // Replace with your actual provider SDK call, e.g.:
  //   Sentry.captureMessage(...) or
  //   otelMeter.histogram(...)
  if (process.env.NODE_ENV === 'production') {
    await fetch(process.env.OBSERVABILITY_INGEST_URL!, {
      method:  'POST',
      headers: { 'Content-Type': 'application/json',
                 'X-Api-Key':   process.env.OBSERVABILITY_API_KEY! },
      body:    JSON.stringify({ ...event, timestamp: Date.now() }),
    });
  } else {
    console.info('[telemetry]', event);
  }
}

export async function reportError(
  action: string,
  err: unknown,
  ctx: UserContext,
  durationMs: number
): Promise<void> {
  const message = err instanceof Error ? err.message : String(err);
  console.error(`[action:${action}] ${message}`, { userId: ctx.userId });

  await reportEvent({
    action, ok: false, durationMs,
    code:   'INTERNAL_ERROR',
    userId: ctx.userId,
    email:  ctx.email,
  });
}

Composing the Full Instrumented Action

Now combine user context, duration measurement, and telemetry reporting into one coherent Server Action. The key rule is: always report before returning — even on the happy path, so you have latency data for successful calls too.

// app/actions/create-post.ts  (final version)
'use server';

import { ok, fail, type ActionResult } from '@/lib/action-result';
import { getUserContext }              from '@/lib/auth-context';
import { reportEvent, reportError }   from '@/lib/telemetry';
import { db }                         from '@/lib/db';

export async function createPost(
  _prev: ActionResult<{ id: string }> | null,
  formData: FormData
): Promise<ActionResult<{ id: string }>> {
  const start = performance.now();
  const ctx   = await getUserContext();

  try {
    const title = (formData.get('title') as string)?.trim();
    if (!title) {
      const dur = performance.now() - start;
      await reportEvent({ action: 'createPost', ok: false,
                          code: 'VALIDATION_ERROR', durationMs: dur,
                          userId: ctx.userId });
      return fail('VALIDATION_ERROR', 'Title is required', dur);
    }

    const post = await db.post.create({ data: { title, authorId: ctx.userId! } });
    const dur  = performance.now() - start;

    await reportEvent({ action: 'createPost', ok: true,
                        durationMs: dur, userId: ctx.userId });
    return ok({ id: post.id }, dur);
  } catch (err) {
    const dur = performance.now() - start;
    await reportError('createPost', err, ctx, dur);
    return fail('INTERNAL_ERROR', 'Failed to create post', dur);
  }
}

Extracting a withAction Higher-Order Wrapper

Duplicating context-fetch and telemetry calls in every action creates noise and inconsistency. Extract a higher-order wrapper, withAction, that handles the boilerplate automatically.

The wrapper:

  • Reads user context once at the start
  • Measures duration around the inner function
  • Reports success and failure telemetry
  • Translates unknown thrown errors into safe ActionFailure values
// lib/with-action.ts
import { ok, fail, type ActionResult } from './action-result';
import { getUserContext, type UserContext } from './auth-context';
import { reportEvent, reportError }        from './telemetry';

type InnerFn<TInput, TOutput> = (
  input: TInput,
  ctx:   UserContext
) => Promise<ActionResult<TOutput>>;

export function withAction<TInput, TOutput>(
  name:  string,
  inner: InnerFn<TInput, TOutput>
) {
  return async (input: TInput): Promise<ActionResult<TOutput>> => {
    const start = performance.now();
    const ctx   = await getUserContext();

    try {
      const result = await inner(input, ctx);
      const dur    = performance.now() - start;

      await reportEvent({
        action: name, ok: result.ok,
        code:   result.ok ? undefined : (result as { code: string }).code,
        durationMs: dur, userId: ctx.userId,
      });
      return result;
    } catch (err) {
      const dur = performance.now() - start;
      await reportError(name, err, ctx, dur);
      return fail('INTERNAL_ERROR', 'An unexpected error occurred', dur);
    }
  };
}

Using withAction in a Real Server Action

With withAction in place, individual action files become concise and focused purely on business logic. All observability wiring is invisible to the developer writing the action.

// app/actions/delete-post.ts
'use server';

import { ok, fail } from '@/lib/action-result';
import { withAction }  from '@/lib/with-action';
import { db }          from '@/lib/db';

export const deletePost = withAction(
  'deletePost',
  async ({ postId }: { postId: string }, ctx) => {
    if (!ctx.userId) {
      return fail('UNAUTHENTICATED', 'You must be logged in', 0);
    }

    const post = await db.post.findUnique({ where: { id: postId } });
    if (!post) {
      return fail('NOT_FOUND', 'Post not found', 0);
    }
    if (post.authorId !== ctx.userId) {
      return fail('FORBIDDEN', 'You do not own this post', 0);
    }

    await db.post.delete({ where: { id: postId } });
    return ok({ deleted: true }, 0);   // duration injected by wrapper
  }
);

// Usage in a Client Component:
// const result = await deletePost({ postId: '...' });
// if (!result.ok) toast.error(result.message);

Connecting to OpenTelemetry Traces

Metric events are useful, but distributed traces let you see exactly where time was spent across DB queries, external API calls, and middleware. Next.js 15 has built-in OpenTelemetry support via the instrumentation.ts file.

Register your OTel SDK once, then create spans inside actions to complement the automatic HTTP spans:

// instrumentation.ts  (Next.js 15 — runs once on server start)
export async function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    const { NodeSDK }             = await import('@opentelemetry/sdk-node');
    const { OTLPTraceExporter }   = await import('@opentelemetry/exporter-trace-otlp-http');
    const { Resource }            = await import('@opentelemetry/resources');
    const { SEMRESATTRS_SERVICE_NAME } = await import('@opentelemetry/semantic-conventions');

    const sdk = new NodeSDK({
      resource: new Resource({
        [SEMRESATTRS_SERVICE_NAME]: 'my-nextjs-app',
      }),
      traceExporter: new OTLPTraceExporter({
        url: process.env.OTEL_EXPORTER_OTLP_ENDPOINT,
      }),
    });

    sdk.start();
  }
}

Adding Custom Spans Inside withAction

Once OTel is registered, you can enrich traces with custom spans directly inside the withAction wrapper. This creates a parent span for the entire action, which automatically parents any child spans created by DB clients or fetch calls during the action's execution.

// lib/with-action.ts  (OTel-enhanced version)
import { trace, SpanStatusCode } from '@opentelemetry/api';
import { ok, fail, type ActionResult } from './action-result';
import { getUserContext, type UserContext } from './auth-context';
import { reportEvent, reportError }        from './telemetry';

const tracer = trace.getTracer('server-actions');

type InnerFn<I, O> = (input: I, ctx: UserContext) => Promise<ActionResult<O>>;

export function withAction<I, O>(name: string, inner: InnerFn<I, O>) {
  return async (input: I): Promise<ActionResult<O>> => {
    return tracer.startActiveSpan(`action.${name}`, async (span) => {
      const start = performance.now();
      const ctx   = await getUserContext();

      span.setAttributes({
        'action.name':   name,
        'user.id':       ctx.userId ?? 'anonymous',
        'user.email':    ctx.email  ?? '',
      });

      try {
        const result = await inner(input, ctx);
        const dur    = performance.now() - start;

        span.setAttributes({ 'action.ok': result.ok, 'action.duration_ms': dur });
        span.setStatus({ code: result.ok ? SpanStatusCode.OK : SpanStatusCode.ERROR });
        span.end();

        await reportEvent({ action: name, ok: result.ok, durationMs: dur, userId: ctx.userId });
        return result;
      } catch (err) {
        const dur = performance.now() - start;
        span.recordException(err as Error);
        span.setStatus({ code: SpanStatusCode.ERROR });
        span.end();

        await reportError(name, err, ctx, dur);
        return fail('INTERNAL_ERROR', 'An unexpected error occurred', dur);
      }
    });
  };
}

Surfacing Action Errors in a Client Error Boundary

Even with perfect server-side telemetry, the client still needs to handle failures gracefully. Use useActionState to relay the ActionResult back to the UI, and pair it with a React Error Boundary for unexpected render errors:

  • useActionState propagates the ActionFailure payload so you can show inline messages
  • A top-level error.tsx in the App Router catches errors that escape action boundaries (e.g. during streaming)
  • Log client-side boundary triggers back to the same telemetry pipeline via a dedicated API route to keep a unified error view

This completes the loop: errors are captured on the server with full context and surfaced on the client with safe, user-friendly messages.

Knowledge Check: Telemetry in Server Actions

Test your understanding of the key design decisions in this lesson.

Lesson Recap: Server Action Telemetry Pipeline

In this lesson you built a complete observability pipeline for Next.js 15 Server Actions:

  • ActionResult discriminated union — a consistent, serialisable return type that distinguishes success from failure without exposing server internals to the client
  • Duration measurement — performance.now() wrapping every action body, captured on both success and error paths
  • User context — reading the session once at the start of each action so every telemetry event carries userId and email
  • Centralised telemetry reporter — a single module that forwards structured events to your observability backend, keeping business logic clean
  • withAction wrapper — a higher-order function that composes context, duration, and telemetry automatically so individual actions stay focused on business logic
  • OpenTelemetry integration — registering the OTel SDK in instrumentation.ts and creating parent spans inside withAction so DB and external API calls appear as child spans in distributed traces
  • Client error surfacing — using useActionState and error.tsx to relay safe failure messages to users while keeping raw errors server-side

Together these layers give you full visibility into every action invocation — who triggered it, whether it succeeded, how long it took, and exactly where it failed.

Sıkça Sorulan Sorular

“Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama” dersi ücretsiz mi?

Evet — “Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama” dersin tüm metni burada web'de ücretsiz olarak okunabilir. Etkileşimli olarak pratik yapmak (yerleşik kod editörü ve 7/24 yapay zeka koçu) ve Next.js 15 Fullstack (App Router + Server Actions) kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. Next.js 15 Fullstack (App Router + Server Actions) kursu toplamda 4 dersten oluşur.

“Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama” dersinde ne öğreneceğim?

İşlem hatalarını ve performans ölçümlerini kullanıcı bağlamıyla birlikte gözlemlenebilirlik arka ucuna bildirin. Next.js 15 Fullstack (App Router + Server Actions) ile uygulamalı kodu tarayıcıda doğrudan çalıştırarak pratik yaparsın ve 7/24 yapay zeka koçu dersi çalışırken sorularını yanıtlar.

Next.js 15 Fullstack (App Router + Server Actions) öğrenmeye başlamak için deneyim gerekli mi?

Önceden deneyim gerekmez. CoddyKit'te Next.js 15 Fullstack (App Router + Server Actions), başlangıçtan ileri seviyeye kadar yapılandırıldığı için buradan başlayabilir veya başından başlayıp kendi hızında ilerleme yapabilirsin. Bu, 4 dersinin 4. dersidir.

“Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama” dersi ne kadar sürer?

Çoğu CoddyKit dersi yaklaşık 5–10 dakika sürer. Her biri kısa ve etkileşimli olduğu için sabit ilerleme yaparsın ve web ile uygulama arasında tam olarak bıraktığın yerden devam edebilirsin.

Bu Next.js 15 Fullstack (App Router + Server Actions) dersinde kod yazıp çalıştırabilir miyim?

Evet. Her Next.js 15 Fullstack (App Router + Server Actions) dersi yerleşik bir kod editörü içerir, bu sayede tarayıcıda gerçek kod yazıp çalıştırabilir ve anlık yapay zeka geri bildirimi alırsın — yerel kurulum gerekli değildir.

Bu kursun tüm dersleri

  1. instrumentation.ts ile OpenTelemetry İzleme
  2. Ayrıntılı error.tsx ve global-error Sınırları
  3. Sunucu ve Edge Genelinde Yapılandırılmış Günlükleme
  4. Sunucu İşlemi Hatalarını ve Telemetriyi Yakalama
← Next.js 15 Fullstack (App Router + Server Actions) Sayfasına Dön