Serverless AWS Lambda Development · Leçon

Déboguer des applications sans serveur

Déboguer des applications sans serveur est une leçon Serverless AWS Lambda Development gratuite sur CoddyKit. Ceci est la leçon 3 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Serverless AWS Lambda Development, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Serverless AWS Lambda Development comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Intro to Debugging Lambda

Debugging serverless applications, especially AWS Lambda functions, presents unique challenges. Unlike traditional applications, Lambdas are stateless and ephemeral.

In this lesson, we'll explore practical techniques for effectively identifying and resolving issues in your Lambda functions, from local testing to interpreting logs.

Why Serverless Debugging is Unique

Traditional debugging often involves stepping through code line-by-line using an IDE. With Lambda, this isn't always straightforward because:

Ephemeral Nature: Functions run only when invoked, then disappear.
Statelessness: No persistent memory between invocations.
Distributed Systems: Issues can arise from interactions between many services.

We rely heavily on logs, metrics, and tracing to understand what's happening.

Local Testing with SAM CLI

One of the most effective ways to debug is to test your Lambda functions locally before deploying them to AWS.

The AWS Serverless Application Model (SAM) CLI allows you to invoke your Lambda functions on your local machine, simulating the AWS Lambda runtime environment.

Faster feedback loop.
Use your familiar local debugging tools.

SAM CLI Local Invoke Demo

Here's a simple Python Lambda function. For local testing, you can simulate an event and context. Try running it!

import json

def lambda_handler(event, context):
    message = event.get('message', 'Hello from Lambda!')
    print(f"Received event: {json.dumps(event)}")
    print(f"Processing message: {message}")
    return {
        'statusCode': 200,
        'body': json.dumps({'response': message})
    }

# This block allows local execution
if __name__ == '__main__':
    # Simulate an event
    test_event = {'message': 'Local debug test'}
    # Simulate a context object
    test_context = type('obj', (object,), {'invoked_function_arn': 'local'})()

    response = lambda_handler(test_event, test_context)
    print("\n--- Lambda Response ---")
    print(json.dumps(response, indent=2))

CloudWatch Logs for Debugging

Once your Lambda is deployed, Amazon CloudWatch Logs becomes your primary tool for understanding its behavior and debugging issues.

Every time your Lambda function is invoked, logs are sent to a dedicated log group. Each invocation gets a unique Request ID, which helps trace its execution.

Log Groups: Contain logs for a specific function.
Log Streams: Specific instances of your function's logs.

Finding Issues in Logs

When an error occurs, the first place to look is CloudWatch Logs. You can:

Filter Logs: Search for keywords like "ERROR", "Exception", or specific messages.
Log Insights: Use powerful query language to analyze logs, group errors, and identify trends.
Request ID: Use the Request ID from the invocation to find all logs related to a specific execution.

Always check the full stack trace for detailed error information.

Debugging with Log Statements

The simplest yet most powerful debugging technique for Lambda is using print() (Python) or console.log() (Node.js) statements.

By strategically adding log statements, you can track variable values, execution paths, and function state at different points in your code. Let's see an example:

import json

def calculate_discount(price, discount_percentage):
    print(f"DEBUG: Initial price: {price}")
    if not isinstance(price, (int, float)) or price < 0:
        raise ValueError("Price must be non-negative.")
    if not isinstance(discount_percentage, (int, float)) or not (0 <= discount_percentage <= 100):
        raise ValueError("Discount must be between 0 and 100.")

    discount_amount = price * (discount_percentage / 100)
    final_price = price - discount_amount
    print(f"DEBUG: Final price: {final_price}")
    return final_price

def lambda_handler(event, context):
    try:
        data = json.loads(event['body'])
        price = data['price']
        discount = data['discount']
        
        final_price = calculate_discount(price, discount)
        
        return {
            'statusCode': 200,
            'body': json.dumps({'originalPrice': price, 'finalPrice': final_price})
        }
    except Exception as e:
        print(f"ERROR: An error occurred: {e}")
        return {
            'statusCode': 400,
            'body': json.dumps({'error': str(e)})
        }

if __name__ == '__main__':
    # Test case 1: Valid input
    test_event_1 = {'body': json.dumps({'price': 100, 'discount': 10})}
    response_1 = lambda_handler(test_event_1, None)
    print("\n--- Test Case 1 Response ---")
    print(json.dumps(response_1, indent=2))

    # Test case 2: Invalid discount
    test_event_2 = {'body': json.dumps({'price': 50, 'discount': 110})}
    response_2 = lambda_handler(test_event_2, None)
    print("\n--- Test Case 2 Response ---")
    print(json.dumps(response_2, indent=2))

Understanding Invocation Errors

Lambda functions can fail for various reasons. It's crucial to distinguish between different error types:

Function Errors: Your code threw an unhandled exception. These appear in CloudWatch Logs with a stack trace.
Invocation Errors: Issues before your code even runs, like permissions errors or payload size limits. These might not even show up in your function's logs directly.
Timeout Errors: Your function exceeded its configured execution time.

CloudWatch metrics and X-Ray (another lesson!) help identify these.

Tracing Request Flow

In complex serverless applications, a single request might involve multiple Lambda functions, API Gateway, SQS, DynamoDB, and more.

Understanding the flow of a request across these services is key to debugging. Use the Request ID (often propagated as x-amzn-RequestId or similar) to correlate logs across different components.

AWS X-Ray (covered in a later lesson) provides visual tracing for this purpose.

Best Practices for Debugging

To minimize debugging headaches, adopt these practices:

Comprehensive Logging: Log inputs, outputs, and key variable states.
Structured Logging: Use JSON logs for easier parsing and querying.
Idempotency: Design functions to produce the same result even if invoked multiple times.
Small Functions: Easier to isolate and test.
Automated Testing: Unit and integration tests catch issues early.

Debugging Challenge

You have a Lambda function that processes user registration. Users report that sometimes, their registration fails, but you don't see any "ERROR" messages in CloudWatch Logs for your Lambda function.

What is the most likely reason for this, and where should you investigate first?

Recap: Debugging Serverless

We've covered essential techniques for debugging your serverless applications:

Local testing with SAM CLI for rapid iteration.
Using CloudWatch Logs to analyze function behavior and identify errors.
Leveraging log statements to trace execution flow.
Understanding different types of Lambda errors.
Best practices for building debuggable serverless functions.

Mastering these will significantly improve your ability to build robust serverless applications.

Questions Fréquemment Posées

La leçon « Déboguer des applications sans serveur » est-elle gratuite ?

Oui — le texte complet de « Déboguer des applications sans serveur » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Serverless AWS Lambda Development, passe à CoddyKit PRO. Le cours Serverless AWS Lambda Development comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Déboguer des applications sans serveur » ?

Découvrez des techniques pour déboguer efficacement les fonctions Lambda, notamment les tests locaux, le débogage à distance et l’interprétation des journaux CloudWatch pour résoudre les problèmes Tu pratiques Serverless AWS Lambda Development avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Serverless AWS Lambda Development ?

Aucune expérience préalable n'est requise. Serverless AWS Lambda Development sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 3 sur 4.

Combien de temps prend la leçon « Déboguer des applications sans serveur » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Serverless AWS Lambda Development ?

Oui. Chaque leçon Serverless AWS Lambda Development inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

Journaux et indicateurs CloudWatch
Gestion des erreurs et nouvelles tentatives
Déboguer des applications sans serveur
Indicateurs personnalisés et alarmes CloudWatch

← Retour à Serverless AWS Lambda Development