AWS Lambda SupportOps Troubleshooting
16 Questions
4 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What information should always be paired with RequestIDs when collecting logs from the customer?

  • Issue start time and end time
  • Function ARN and timestamp (with timezone) (correct)
  • X-Ray trace ID
  • CloudTrail verification
  • In the event of failure to identify, isolate, or mitigate an issue, what is the next recommended action according to the text?

  • Refer to CloudTrail for verification
  • Escalate to Lambda SupportOps (correct)
  • Request reproduction steps
  • Reach out to Local Lambda SME or PSAP
  • What is emphasized as important when checking X-Ray traces?

  • Collecting the raw trace, not just the X-Ray trace ID (correct)
  • Checking CloudTrail for verification
  • Escalating to Local Lambda SME or PSAP
  • Asking for reproduction steps
  • Before cutting a ticket to Lambda Support Ops, what should be attempted if due diligence fails to resolve the issue?

    <p>Reaching out to Local Lambda SME or PSAP</p> Signup and view all the answers

    What is the minimum and required information needed for performing a log dive in a Lambda Front End (FE) log?

    <p>RequestID, AWS Region, and timestamp</p> Signup and view all the answers

    What type of issues do FE logs typically not help with diagnosing?

    <p>Timeout issues</p> Signup and view all the answers

    What is out of scope for Support Ops/Service Team?

    <p>Joining a customer bridge</p> Signup and view all the answers

    What should be the appropriate severity for immediate production pain?

    <p>Sev2</p> Signup and view all the answers

    What information is strongly recommended to include when reporting an issue?

    <p>Request IDs with timestamps</p> Signup and view all the answers

    What type of logs do not provide any information on what happened in the function code?

    <p>FE logs</p> Signup and view all the answers

    What is the first step for all requests related to Lambda Support Operations Team?

    <p>Go through Lambda Service Team first</p> Signup and view all the answers

    Which team should tickets be moved to for actual issues with the Lambda service or high severity issues?

    <p>Lambda Service Team CTIs</p> Signup and view all the answers

    What capability does the Service Team have in relation to network issues?

    <p>More capability than Support Ops/Service Team for debugging network issues</p> Signup and view all the answers

    What type of ticket severity is appropriate for time-sensitive issues needing prompt attention but can wait until business hours?

    <p>Sev2.5</p> Signup and view all the answers

    What does 'PFR' stand for in relation to Enterprise Customers?

    <p>Product Feature Request</p> Signup and view all the answers

    What must be filled out with all the requested details for all requests related to Lambda Support Operations Team?

    <p>SIM template</p> Signup and view all the answers

    Study Notes

    Collecting Logs from Customers

    • When collecting logs from customers, the RequestID should always be paired with the following information:

    Issue Identification and Mitigation

    • In the event of failure to identify, isolate, or mitigate an issue, the next recommended action is to escalate the issue.

    Checking X-Ray Traces

    • When checking X-Ray traces, it is important to pay attention to the entire distributed trace, including downstream calls and errors.

    Lambda Support Ops Tickets

    • Before cutting a ticket to Lambda Support Ops, all due diligence should be attempted to resolve the issue first.
    • The minimum and required information needed for performing a log dive in a Lambda Front End (FE) log includes the RequestID and relevant logs.

    FE Logs

    • FE logs typically do not help with diagnosing issues related to function code or backend services.

    Support Ops/Service Team Scope

    • Out of scope for Support Ops/Service Team are issues related to network connectivity and device-level issues.
    • The Service Team has the capability to assist with network issues up to the AWS edge.

    Issue Reporting

    • When reporting an issue, it is strongly recommended to include the RequestID, relevant logs, and detailed steps to reproduce the issue.

    Log Types

    • Cold Start logs do not provide any information on what happened in the function code.

    Lambda Support Operations Team

    • The first step for all requests related to Lambda Support Operations Team is to provide the required information, including the RequestID and relevant logs.
    • Tickets should be moved to the Lambda Service Team for actual issues with the Lambda service or high severity issues.

    Ticket Severity

    • A severity of High is appropriate for immediate production pain, while a severity of Urgent is suitable for time-sensitive issues needing prompt attention but can wait until business hours.

    Enterprise Customers

    • 'PFR' stands for 'Partner-Facing Representative' in relation to Enterprise Customers.

    Request Requirements

    • The request form must be filled out with all the requested details for all requests related to Lambda Support Operations Team.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Description

    This quiz covers the necessary steps to take when escalating AWS Lambda issues to SupportOps, including collecting relevant logs, identifying issue start time, end time, and frequency, checking for setup changes, and verifying with CloudTrail and X-Ray traces.

    More Like This

    Use Quizgecko on...
    Browser
    Browser