Monitoramento e registro
Configure monitoramento e registro para suas aplicações na borda, a fim de acompanhar o desempenho e depurar problemas.
Monitoramento e registro é uma aula grátis de Edge Computing with Cloudflare Workers & Deno no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Edge Computing with Cloudflare Workers & Deno, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Edge Computing with Cloudflare Workers & Deno inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
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!
Perguntas Frequentes
A aula “Monitoramento e registro” é grátis?
Sim — o texto completo de “Monitoramento e registro” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Edge Computing with Cloudflare Workers & Deno, atualize para CoddyKit PRO. O curso de Edge Computing with Cloudflare Workers & Deno inclui 4 aulas no total.
O que vou aprender em “Monitoramento e registro”?
Configure monitoramento e registro para suas aplicações na borda, a fim de acompanhar o desempenho e depurar problemas. Você pratica Edge Computing with Cloudflare Workers & Deno com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Edge Computing with Cloudflare Workers & Deno?
Nenhuma experiência prévia é necessária. Edge Computing with Cloudflare Workers & Deno no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.
Quanto tempo leva a aula “Monitoramento e registro”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Edge Computing with Cloudflare Workers & Deno?
Sim. Cada aula de Edge Computing with Cloudflare Workers & Deno inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Estratégias de cache
- Inicializações a frio e aquecimentos
- Monitoramento e registro
- Tamanho do pacote e otimização de código