การสังเกตการณ์ระบบ: การบันทึกเหตุการณ์ ตัวชี้วัด การติดตามการทำงาน

In this lesson, we'll explore observability, a crucial concept for managing complex software systems, especially LLM applications.

Observability means understanding the internal state of a system by examining the data it produces. Think of it as having X-ray vision into your application's behavior.

For LLM apps, this helps us answer critical questions like:

• Why is a request slow?
• Is the RAG retrieval working as expected?
• Are we incurring unexpected costs?

Logs are timestamped records of events that happen within your application. They are like a diary of your system's activities.

For LLM applications, logs are essential for:

• Tracking incoming user prompts.
• Storing responses from the LLM.
• Recording intermediate steps in a RAG pipeline (e.g., documents retrieved).
• Capturing errors or warnings.

They provide detailed contextual information for debugging and post-mortem analysis.

Here's a simple Python example demonstrating how to log an LLM interaction. We're using Python's built-in logging module.

This helps you see exactly what prompts were sent and what responses were received, which is vital for debugging and improving your application.

Metrics are numerical measurements collected over time, providing aggregated insights into your system's health and performance.

Unlike logs, which are individual events, metrics are typically quantitative values that can be visualized as graphs and dashboards. Key metrics for LLM apps include:

• Latency: How long it takes for the LLM to respond.
• Token Usage: Input/output tokens consumed per request.
• Error Rate: Percentage of failed LLM calls or RAG retrievals.
• Cache Hit Rate: How often cached responses are used.

You can collect custom metrics to understand specific aspects of your LLM application. This example shows how to track the number of LLM calls and their average latency.

In a real-world scenario, you'd send these metrics to a monitoring system like Prometheus or Datadog.

Tracing is about following a single request as it flows through multiple services and components in a distributed system. This is especially vital for RAG applications that involve many steps: user input, embedding generation, vector DB lookup, LLM call, etc.

A trace visualizes the entire journey of a request, showing the exact path it took and the time spent in each operation.

A trace is a complete end-to-end journey of a request. It's composed of multiple spans.

• A span represents a single operation or unit of work within a trace (e.g., 'retrieve documents', 'call embedding model', 'invoke LLM').
• Spans have a parent-child relationship, forming a tree structure that shows dependencies.
• Context propagation ensures that a unique trace ID follows the request across different services, linking all related spans together.

This helps pinpoint bottlenecks or failures across microservices.

While implementing tracing from scratch is complex, tools like OpenTelemetry (an open-source observability framework) provide standardized ways to instrument your code.

You'd use OpenTelemetry SDKs to:

• Start a new trace when a request comes in.
• Create new spans for each significant operation (e.g., a function call to a vector database or an LLM API).
• Propagate the trace context to downstream services.

This allows you to visualize the full request flow in a tracing UI.

Logs, metrics, and traces are often called the "observability triangle" because they offer complementary views of your system:

• Logs: The granular details and events.
• Metrics: The aggregated numbers and trends.
• Traces: The end-to-end journey of a request.

Together, they provide a comprehensive understanding of your LLM application's behavior, making it easier to diagnose issues, optimize performance, and ensure reliability in production.

Congratulations! You've explored the world of observability for LLM applications.

• We defined observability as understanding internal system state from external data.
• We learned about logs for detailed event recording.
• We covered metrics for aggregated performance measurements.
• We understood traces for visualizing end-to-end request flows.

By integrating these three pillars, you gain powerful insights, enabling you to build more reliable, performant, and cost-efficient LLM systems.