Edge Computing with Cloudflare Workers & Deno · Lektion

Monitoring und Logging

Richten Sie Monitoring und Logging für Ihre Edge-Anwendungen ein, um die Leistung zu verfolgen und Probleme zu beheben.

Monitoring und Logging ist eine kostenlose Edge Computing with Cloudflare Workers & Deno-Lektion auf CoddyKit. Dies ist Lektion 3 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Edge Computing with Cloudflare Workers & Deno-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Edge Computing with Cloudflare Workers & Deno-Kurs umfasst insgesamt 4 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

Why Monitor & Log Edge Apps?

When your applications run at the edge, they're distributed globally. This makes it challenging to know what's happening without good visibility.

Monitoring helps you track performance metrics like request times and error rates across your entire system. Logging gives you detailed records of individual events, like requests or errors, which are crucial for debugging.

Basic Logging: console.log

The simplest way to log information in a Cloudflare Worker is by using console.log(). This works much like logging in a browser or Node.js environment.

Messages sent to console.log() are captured by Cloudflare and can be viewed in your Worker's dashboard or exported using Logpush.

Basic Logging in Action

Try running this Worker. It logs the incoming request's URL to the console. When you test it, check your Worker's logs in the Cloudflare dashboard to see the output.

export default {
  async fetch(request, env, ctx) {
    console.log("Request received for:", request.url);
    return new Response("Hello from basic logging!");
  }
};

The Need for Structured Logs

While console.log() is easy, plain text logs can be hard to parse and analyze at scale. Imagine sifting through thousands of lines of text!

Structured logging involves outputting logs in a consistent, machine-readable format, like JSON. This makes it much easier for monitoring tools to process and query your logs.

Cloudflare Logpush Overview

Cloudflare's Logpush service allows you to export your Worker logs to various destinations, such as cloud storage (AWS S3, Google Cloud Storage) or analytics platforms.

This is essential for long-term storage, advanced querying, and integrating with your existing monitoring infrastructure.

What to Include in Logs?

Good structured logs contain useful context. Consider including:

Timestamp: When the event occurred.
Level: (e.g., INFO, WARN, ERROR) for severity.
Request ID: To trace a single request through its lifecycle.
URL & Method: Details of the incoming request.
Latency: How long the operation took.
Error Details: Stack traces, error messages.

Structured Logging Example

This Worker logs request details as a JSON string, including a simple latency measurement. This format is easily parsable by log analysis tools.

export default {
  async fetch(request, env, ctx) {
    const start = Date.now();
    const response = new Response("Hello from structured logs!");
    const latency = Date.now() - start;

    const logEntry = {
      timestamp: new Date().toISOString(),
      level: "INFO",
      url: request.url,
      method: request.method,
      latencyMs: latency,
      requestId: crypto.randomUUID()
    };
    console.log(JSON.stringify(logEntry));

    return response;
  }
};

Introduction to Edge Metrics

While logs tell you 'what happened,' metrics tell you 'how much' or 'how often.' Metrics are numerical measurements captured over time, used to track the health and performance of your application.

Common metrics include requests per second, error rates, CPU usage, and memory consumption. They are aggregated and visualized in dashboards.

Custom Metrics in Workers

Cloudflare Workers provide built-in analytics, but you can also add custom metrics. One simple way is to use response headers to expose performance data that can be scraped or analyzed.

Here, we add a X-Worker-Latency header. More advanced metrics might use external services or Cloudflare's ctx.waitUntil to send data.

export default {
  async fetch(request, env, ctx) {
    const start = Date.now();
    const response = new Response("Hello from custom metrics!");
    const latency = Date.now() - start;

    // Add a custom header as a simple metric
    response.headers.set("X-Worker-Latency", latency.toString());

    console.log(`Request processed in ${latency}ms`);
    return response;
  }
};

Monitoring Tools & Dashboards

Once you have logs and metrics, you need tools to make sense of them. Cloudflare provides basic analytics, but for advanced analysis, you'll integrate with:

Log Management Systems: Splunk, ELK Stack, DataDog, Sumo Logic.
Monitoring Platforms: Grafana, Prometheus, New Relic, Dynatrace.

These tools help you visualize trends, set up alerts, and quickly identify issues.

Quick Check on Logging

You are debugging an intermittent error in your Cloudflare Worker. You've been using console.log("Error occurred!") to catch issues.

Which change would MOST improve your ability to diagnose the problem quickly?

Recap: Monitoring & Logging

Great job! In this lesson, you learned about the critical role of monitoring and logging for edge applications.

console.log() is your basic logging tool.
Structured logging (e.g., JSON) provides machine-readable, actionable insights.
Cloudflare Logpush helps export logs for advanced analysis.
Metrics track performance trends, often exposed via custom headers or dedicated services.
Using external monitoring tools can greatly enhance visibility and debugging capabilities.

Keeping an eye on your edge apps ensures they perform optimally!

Häufig gestellte Fragen

Ist die Lektion „Monitoring und Logging“ kostenlos?

Ja — der vollständige Text von „Monitoring und Logging“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Edge Computing with Cloudflare Workers & Deno-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Edge Computing with Cloudflare Workers & Deno-Kurs umfasst insgesamt 4 Lektionen.

Was lerne ich in „Monitoring und Logging“?

Richten Sie Monitoring und Logging für Ihre Edge-Anwendungen ein, um die Leistung zu verfolgen und Probleme zu beheben. Du übst Edge Computing with Cloudflare Workers & Deno mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um Edge Computing with Cloudflare Workers & Deno zu starten?

Keine Vorkenntnisse erforderlich. Edge Computing with Cloudflare Workers & Deno auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 3 von 4.

Wie lange dauert die Lektion „Monitoring und Logging“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser Edge Computing with Cloudflare Workers & Deno-Lektion Code schreiben und ausführen?

Ja. Jede Edge Computing with Cloudflare Workers & Deno-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

← Zurück zu Edge Computing with Cloudflare Workers & Deno