Serverless brings enormous opportunities for speed, scale and agility. But it also introduces new complexities and turns troubleshooting and remediation on their heads. Cloud-native applications built using serverless architectures are highly complex and distributed, and often are made up of many dynamic microservices and third-party services and components. Traditional monitoring practices use agents that sit within your own code to extract telemetry data, which you have to dig through to find the root cause of an error.

In a perfect world, we'd catch all an app's errors and bugs in development or QA. But as every developer knows, this isn’t reality; stuff still breaks in production where risk and complexity is high. With hundreds, thousands or even millions of invocations, piles of log data and blind spots across distributed components, troubleshooting remains a significant burden on developers, especially for cloud-native applications. Where do you start? What do you look for? How can you understand how bad the issue is and what else it has impacted? Why is this so hard?

In this webinar, we’ll dive into how you can troubleshoot serverless apps safely and quickly in production without using logs.

Key Takeaways:

• How to search and identify invocations and requests without having to use logs
• What metrics you should set and alerts you should monitor when dealing with serverless apps
• Why you need more than logs to get sufficient data for troubleshooting in production
• How to customize error types to fit your use case