AWS has launched the public preview of OpenTelemetry (OTel) metrics support within Amazon CloudWatch, enabling developers to send metrics directly via the OTLP protocol. This update completes CloudWatch's support for logs, traces, and metrics using open standards.
- Support for high-cardinality metrics with up to 150 labels per metric.
- Integration of PromQL, allowing users to use Prometheus query language within the CloudWatch console and Managed Grafana.
- Automatic enrichment of ingested metrics with AWS resource metadata such as account ID, Region, and resource tags.
- Support for high-cardinality metrics with up to 150 labels per metric.
- Integration of PromQL, allowing users to use Prometheus query language within the CloudWatch console and Managed Grafana.
- Automatic enrichment of ingested metrics with AWS resource metadata such as account ID, Region, and resource tags.
AWS has released the general availability of its DevOps Agent, a generative AI assistant designed to automate incident investigation and operational tasks. Built on Amazon Bedrock AgentCore, the tool integrates with observability platforms, code repositories, and CI/CD pipelines to autonomously triage issues and correlate telemetry data. New capabilities include support for investigating applications in Azure and on-premises environments, custom agent skills, and personalized reporting.
Key highlights:
* Autonomous incident investigation triggered by webhooks from sources like CloudWatch or PagerDuty.
* Integration with major tools including Datadog, Grafana, Splunk, GitHub, and GitLab.
* Reported performance improvements of up to 75% lower MTTR during preview.
* Pricing model based on cumulative time spent on operational tasks per second.
Key highlights:
* Autonomous incident investigation triggered by webhooks from sources like CloudWatch or PagerDuty.
* Integration with major tools including Datadog, Grafana, Splunk, GitHub, and GitLab.
* Reported performance improvements of up to 75% lower MTTR during preview.
* Pricing model based on cumulative time spent on operational tasks per second.
Amazon Web Services (AWS) recently made a significant move by laying off approximately 40% of its DevOps staff. This decision wasn't a sign of downsizing, but rather a strategic shift towards automation and a new tool called 'Dahlia'. This article explores the reasons behind the layoffs, the capabilities of Dahlia, and its potential impact on the future of DevOps.
The article details Amazon Web Services' (AWS) recent decision to lay off a significant portion (around 40%) of its DevOps workforce, specifically those involved in managing and maintaining its own internal infrastructure. This isn't a sign of AWS abandoning DevOps, but rather a strategic shift *towards* fully embracing a "platform engineering" approach and leveraging automation tools.
* **Shift to Platform Engineering:** AWS is building internal "developer platforms" – self-service tools and standardized components – to empower application development teams to manage their own infrastructure and deployments with less reliance on centralized DevOps teams.
* **Key Tools Driving the Change:** The article highlights three main tools enabling this transition:
* **Pulumi:** An Infrastructure-as-Code (IaC) tool allowing developers to define infrastructure using familiar programming languages (Python, JavaScript, Go, etc.).
* **Crossplane:** An open-source Kubernetes add-on that extends Kubernetes to manage infrastructure across multiple cloud providers.
* **Backstage:** A developer portal created by Spotify, now open-source, that provides a centralized interface for developers to discover, create, and manage software components and infrastructure.
* **Impact of the Layoffs:** The layoffs were concentrated in teams traditionally responsible for manual infrastructure provisioning and maintenance. The remaining DevOps staff are being re-focused on building and maintaining the internal developer platforms.
* **Wider Industry Trend:** This move by AWS reflects a broader trend in the industry towards platform engineering, driven by the need for faster innovation, increased developer productivity, and reduced operational overhead.
In essence, AWS is automating away much of the traditional DevOps work, allowing developers to self-serve their infrastructure needs through these platform tools. This is a strategic move to scale its internal development efforts and accelerate innovation.
The article details Amazon Web Services' (AWS) recent decision to lay off a significant portion (around 40%) of its DevOps workforce, specifically those involved in managing and maintaining its own internal infrastructure. This isn't a sign of AWS abandoning DevOps, but rather a strategic shift *towards* fully embracing a "platform engineering" approach and leveraging automation tools.
* **Shift to Platform Engineering:** AWS is building internal "developer platforms" – self-service tools and standardized components – to empower application development teams to manage their own infrastructure and deployments with less reliance on centralized DevOps teams.
* **Key Tools Driving the Change:** The article highlights three main tools enabling this transition:
* **Pulumi:** An Infrastructure-as-Code (IaC) tool allowing developers to define infrastructure using familiar programming languages (Python, JavaScript, Go, etc.).
* **Crossplane:** An open-source Kubernetes add-on that extends Kubernetes to manage infrastructure across multiple cloud providers.
* **Backstage:** A developer portal created by Spotify, now open-source, that provides a centralized interface for developers to discover, create, and manage software components and infrastructure.
* **Impact of the Layoffs:** The layoffs were concentrated in teams traditionally responsible for manual infrastructure provisioning and maintenance. The remaining DevOps staff are being re-focused on building and maintaining the internal developer platforms.
* **Wider Industry Trend:** This move by AWS reflects a broader trend in the industry towards platform engineering, driven by the need for faster innovation, increased developer productivity, and reduced operational overhead.
In essence, AWS is automating away much of the traditional DevOps work, allowing developers to self-serve their infrastructure needs through these platform tools. This is a strategic move to scale its internal development efforts and accelerate innovation.
SRE.ai, a Y Combinator-backed startup, has raised $7.2 million to develop AI agents that automate complex enterprise DevOps workflows, offering chat-like experiences across multiple platforms.
The article discusses the increasing complexity of Kubernetes and suggests that Silicon Valley is exploring alternative technologies for container orchestration, citing a benchmark showing a stripped-down stack outperforming Kubernetes.
The article discusses the potential shift away from YAML in Kubernetes 2.0, citing a leaked dashboard photo and the high percentage of production outages linked to YAML misconfigurations. It suggests a new command-line interface is being used for deployments.
