Azure App Service is a platform-as-a-service (PaaS) offering for deploying applications to the cloud without worrying about infrastructure. App Service’s “serverless” approach removes the need to provision or manage the servers that run your applications, which provides flexibility, scalability, and ease of use. However, App Service also introduces infrastructure-like considerations that can impact performance and costs.
In a serverless application, AWS Lambda functions are typically invoked by JSON-formatted events from other AWS services—like API Gateway, S3, and DynamoDB—and respond with JSON-formatted payloads. Having visibility into these function request and response payloads can provide context around your function invocations and help you uncover the root causes of Lambda function failures.
Datadog’s template variables help you quickly scope your dashboards to specific contexts using tags, so you can visualize data from only the hosts, containers, services, or any other tagged objects you care about. This helps you build more flexible dashboards so you can access the insights you’re looking for as quickly as possible. We’re proud to announce new features for the template variable workflow that enable you to make highly dynamic, shareable dashboards more efficiently.
Unsurprisingly, application crashes due to fatal errors can be a major pain point for iOS users. Recent research shows that roughly 20 percent of mobile application uninstalls were due to crashes or other code errors. As a developer, it’s paramount to manage this potential churn by capturing comprehensive crash data in order to track, triage, and debug recurring issues in your iOS apps.
AWS Graviton2 processors use the Arm architecture to provide high-efficiency, low-cost computing. AWS already offers the ability to provision EC2 instances powered by Graviton2, and Datadog is proud to partner with them for the launch of new Graviton2 compute resources for Lambda functions. In this post, we’ll discuss how Datadog can provide deep visibility into your Lambda functions across whichever platform you’re using.
After you have stopped an incident from affecting your customers, you need a more thorough investigation in order to prevent similar incidents in the future. Postmortems record the root causes of an incident and provide insights for making your systems more resilient. At the same time, postmortems can be difficult to produce, since they require deeper analysis and coordination between teammates who are busy with the next development cycle.
Code profilers offer detailed insight into the efficiency of application code by measuring things like the execution time and resource utilization of a service. Datadog’s always-on, low overhead Continuous Profiler provides snapshots of code performance for a service that are tagged with key metadata (e.g., region, service, release), so you can easily identify and optimize inefficient code.
Whether running on a fully cloud-hosted environment, on-premise servers, or a hybrid solution, modern services and applications are heavily reliant on network and DNS performance. This makes comprehensive visibility into your network a key part of monitoring application health and performance. But as your applications grow in scale and complexity, gaining this visibility is challenging.
Netlify is a Jamstack web development platform that lets customers build and deploy dynamic, highly performant web apps. By uniting popular JavaScript frameworks, developer tools, and APIs into streamlined workflows, Netlify helps teams rapidly spin up and ship common Jamstack use cases, including e-commerce stores, SaaS applications, and corporate sites. Netlify supports these deployments with an integrated CI/CD tool, global multi-cloud edge network, and serverless backend.
Amazon Elastic Kubernetes Service (EKS) is a cloud-based compute platform that includes a fully managed Kubernetes control plane in order to simplify cluster operations. AWS introduced EKS Anywhere to bring the operational ease of EKS to organizations that manage on-premise environments (e.g., to meet data sovereignty requirements).
