# observability

Observability is the ability to understand a complex system's internal state from its external telemetry, supporting the operation, troubleshooting, and security of software systems and cloud computing environments.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Top 13 Microservices Interview Questions Answered

DevFeed: [Top 13 Microservices Interview Questions Answered](<https://devfeed.tech/articles/top-13-microservices-interview-questions-answered-146768.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/microservices-interview-questions>)

Author: Neo Kim

Published: 2026-11-20T12:02:22Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [Microservices](<https://devfeed.tech/topics/microservices.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [observability](<https://devfeed.tech/topics/observability.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [monolithic-architecture](<https://devfeed.tech/topics/monolithic-architecture.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [questions](<https://devfeed.tech/tags/questions.md>), [top](<https://devfeed.tech/tags/top.md>)

### AI overview

The article presents 13 microservices interview questions and stresses weighing operational costs against benefits. Microservices enable independent releases and scaling, but introduce network failures, distributed data, and tooling needs; for a small team or new product, it recommends starting with a modular monolith and extracting services when concrete pressures emerge. It explains boundaries based on business capabilities and bounded contexts, service-owned data with APIs or event-fed copies, and sagas with compensating actions for workflows spanning services. Other guidance distinguishes API gateways from load balancers and service meshes, client-side from server-side discovery, and SOA from microservices. It also covers circuit breakers, distributed tracing, shared rate-limit counters across gateway instances, and REST conventions such as idempotency keys for retried order requests.

### Source excerpt

#205: Ace Software Engineering Job Interviews

## Datadog LLM Observability: Features, Pricing, and Alternatives

DevFeed: [Datadog LLM Observability: Features, Pricing, and Alternatives](<https://devfeed.tech/articles/datadog-llm-observability-features-pricing-and-alternatives-145962.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/ai/datadog-llm-observability>)

Author: John Blust

Published: 2026-11-20T11:51:52.599709Z

Content type: article

Language: en

Sources: [New Relic](<https://devfeed.tech/sources/new-relic.md>)

Topics: [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [observability](<https://devfeed.tech/topics/observability.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [phoenix](<https://devfeed.tech/topics/phoenix.md>), [LangChain](<https://devfeed.tech/topics/langchain.md>), [dynatrace](<https://devfeed.tech/topics/dynatrace.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-monitoring](<https://devfeed.tech/tags/ai-monitoring.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [compare](<https://devfeed.tech/tags/compare.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [devops](<https://devfeed.tech/tags/devops.md>), [evaluations](<https://devfeed.tech/tags/evaluations.md>), [features](<https://devfeed.tech/tags/features.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-observability](<https://devfeed.tech/tags/llm-observability.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [new-relic](<https://devfeed.tech/tags/new-relic.md>), [observability](<https://devfeed.tech/tags/observability.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

### AI overview

Datadog LLM Observability, now called Agent Observability, traces model calls and agent workflows, evaluates quality and safety, supports prompt experiments, and tracks latency, tokens, errors, and costs. It is a standalone product billed by model-call spans; tool, retrieval, and workflow spans do not count. Both listed plans include core tracing and evaluation features, and annual Pro pricing starts at $160 per month, with retention add-ons affecting per-span rates. Alternatives differ in approach: New Relic connects AI telemetry to existing APM, including optional eBPF monitoring; Langfuse offers a self-hostable core; LangSmith emphasizes agent tracing and evaluation workflows; and Arize Phoenix supports local deployment with OpenTelemetry-based instrumentation. The text notes that Datadog can correlate with its other products through shared trace IDs and supports Python, Node.js, Java, OpenTelemetry, and HTTP API integration.

### Source excerpt

An objective look at Datadog LLM Observability: tracing, evaluations, how pricing works, and how alternatives like New Relic AI Monitoring compare.

## Agentic AI repeats same old enterprise adoption cycle

DevFeed: [Agentic AI repeats same old enterprise adoption cycle](<https://devfeed.tech/articles/agentic-ai-repeats-same-old-enterprise-adoption-cycle-146087.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4249734/agentic-ai-repeats-same-old-enterprise-adoption-cycle.html>)

Author: David Linthicum

Published: 2026-11-20T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Enterprise Architecture](<https://devfeed.tech/topics/enterprise-architecture.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [observability](<https://devfeed.tech/topics/observability.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-emerging-technology-generative-ai](<https://devfeed.tech/tags/artificial-intelligence-emerging-technology-generative-ai.md>), [automate](<https://devfeed.tech/tags/automate.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [decision](<https://devfeed.tech/tags/decision.md>), [emerging-technology](<https://devfeed.tech/tags/emerging-technology.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [logging](<https://devfeed.tech/tags/logging.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [project](<https://devfeed.tech/tags/project.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

A distributor's agentic AI sales system ran successfully, but after supporting integration, governance, security, testing and operational costs were included, it cost roughly 20 times as much as a traditional architecture for about the same ROI. The article argues that agents are most useful when work requires interpretation, adaptation and semi-autonomous action; stable, rules-based or highly regulated workflows may be served more economically by conventional applications, workflow engines, rules or API integration. It recommends starting with measurable business value and assessing production costs and governance needs rather than adopting an architecture because it is fashionable. The text compares this adoption pattern with SOA, microservices and cloud-native systems, each of which can deliver benefits but also impose complexity when used without a fitting need or organizational maturity.

### Source excerpt

The pitch sounded perfect. A large regional distributor needed to build a new sales transaction management system. The goal was straightforward: automate parts of order intake, discount approvals, exception handling, customer communications, and inventory checks. It was not a trivial system, but it was also something the industry had built before. Then the vendor presentations began. Every software provider seemed to have a new agentic AI story. Their platforms had agents that could make decisions, orchestrate workflows, interpret customer intent, route exceptions, and learn from business context. One vendor described its offering as a common LLM brain that could make decisions as if the company had hired 10,000 experts, except those experts were not on the payroll. That line was from an actual sales pitch, and it landed well in the boardroom. The company decided to go agentic. The architecture would use AI agents to manage decision flows, invoke tools, check policies, interact with enterprise systems, and escalate only when needed. It looked modern. It looked strategic. It looked like the future. Then reality arrived. Building the system required far more integration work than expected. Each agent needed access to clean data, governed APIs, business rules, security controls, observability, exception handling, and human override mechanisms. The team had to build guardrails around decisions, logging around reasoning, test harnesses for unpredictable outcomes, and new operational processes for things traditional systems handled more predictably. Costs ballooned. Security reviews took longer. Operational complexity increased. The project ultimately ran fine once in production, but six months later, the company realized the uncomfortable truth: the system cost roughly 20 times more than a traditional architecture would have cost when all supporting complexity was included, and it delivered about the same ROI. I am hearing versions of this story once or twice a week from

## AWS Lambda Durable Functions observability with OpenTelemetry

DevFeed: [AWS Lambda Durable Functions observability with OpenTelemetry](<https://devfeed.tech/articles/aws-lambda-durable-functions-observability-with-opentelemetry-144754.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/aws-lambda-durable-functions-observability-with-opentelemetry/>)

Author: Ricardo Marques

Published: 2026-11-19T19:09:43Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [observability](<https://devfeed.tech/topics/observability.md>), [serverless monitoring](<https://devfeed.tech/topics/serverless-monitoring.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [durable-functions](<https://devfeed.tech/tags/durable-functions.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [span](<https://devfeed.tech/tags/span.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

The `aws-durable-execution-sdk-python-otel` plugin assigns deterministic trace IDs so invocations of one AWS Lambda Durable Functions execution can appear as a unified trace, with spans reflecting operation wall-clock time and avoiding duplicate spans during replay. Setup requires Python 3.11+, the ADOT Lambda layer, X-Ray active tracing and write permissions, and passing `InvocationOtelPlugin` to the durable execution handler. The post distinguishes execution view, which groups work under the workflow span but depends on the vendor's span-ingestion window, from invocation view, which can export shorter invocation spans sooner; the final workflow span still covers the full execution and may be rejected if too old. Logger enrichment adds trace and span IDs to logs by default. The ADOT layer adds cold-start and memory overhead (about 40-60 MB); the post recommends measuring impact, naming durable operations, and using sampling to manage trace costs. The excerpt's walkthrough covers a sequential workflow with a human approval callback, not every SDK primitive or failure path.

### Source excerpt

A single AWS Lambda Durable Functions workflow can span many invocations, fragmenting its traces. This post shows how the OpenTelemetry plugin for the AWS Durable Execution SDK generates deterministic trace IDs that unify every invocation into one distributed trace, and how to set it up, read the traces, and apply best practices.

## The internet needs a nap (and you do, too)

DevFeed: [The internet needs a nap (and you do, too)](<https://devfeed.tech/articles/the-internet-needs-a-nap-and-you-do-too-144581.md>)

Original publisher: [Read original article](<https://blog.talosintelligence.com/the-internet-needs-a-nap-and-you-do-too/>)

Author: William Largent

Published: 2026-11-19T19:00:00Z

Content type: opinion

Language: en

Sources: [Cisco Talos Blog](<https://devfeed.tech/sources/cisco-talos-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [observability](<https://devfeed.tech/topics/observability.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [1-5](<https://devfeed.tech/tags/1-5.md>), [17](<https://devfeed.tech/tags/17.md>), [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [about](<https://devfeed.tech/tags/about.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [actor](<https://devfeed.tech/tags/actor.md>), [admin](<https://devfeed.tech/tags/admin.md>), [after](<https://devfeed.tech/tags/after.md>), [agencies](<https://devfeed.tech/tags/agencies.md>), [alert](<https://devfeed.tech/tags/alert.md>), [all](<https://devfeed.tech/tags/all.md>), [internet](<https://devfeed.tech/tags/internet.md>), [news](<https://devfeed.tech/tags/news.md>), [over](<https://devfeed.tech/tags/over.md>), [patching](<https://devfeed.tech/tags/patching.md>), [stop](<https://devfeed.tech/tags/stop.md>), [takes](<https://devfeed.tech/tags/takes.md>), [threat-source-newsletter](<https://devfeed.tech/tags/threat-source-newsletter.md>)

### AI overview

The newsletter urges security teams to make time for steady maintenance amid a constant stream of incidents: inventory systems and owners, identify unsupported or hard-to-patch applications, keep systems updated, and learn normal network activity so anomalies are easier to spot. It stresses that patching alone is not a realistic answer and that people need time to assess alerts. Its featured alert is Java4Shell (CVE-2026-114938), an OpenJDK flaw described as enabling unauthenticated remote code execution on Java 17.0.6 and later on x86-64 CPUs with AVX-512 VBMI. No exploitation had been observed at publication. The text recommends applying the update; if that is not immediately possible, disabling AVX-512 at JVM startup with `-XX:UseAVX=2` is a mitigation for x86-64 only, and ARM systems may fail to start with that option. It also recommends the blog's Snort rules and Splunk detections.

### Source excerpt

Bill takes a break from the non-stop breaking news to promote prioritizing environmental awareness and team stability over reactive patching.

## How to find at-risk Pub/Sub messages across Google Cloud projects

DevFeed: [How to find at-risk Pub/Sub messages across Google Cloud projects](<https://devfeed.tech/articles/how-to-find-at-risk-pub-sub-messages-across-google-cloud-projects-146205.md>)

Original publisher: [Read original article](<https://www.dynatrace.com/news/blog/how-to-find-at-risk-pub-sub-messages-across-google-cloud-projects/>)

Author: Stefan Penner

Published: 2026-11-19T16:31:04Z

Content type: tutorial

Language: en

Sources: [Dynatrace news](<https://devfeed.tech/sources/dynatrace-news.md>)

Topics: [cloud pub/sub](<https://devfeed.tech/topics/cloud-pub-sub.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [Cloud Monitoring](<https://devfeed.tech/topics/cloud-monitoring.md>), [Cloud Dataflow](<https://devfeed.tech/topics/cloud-dataflow.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-apis](<https://devfeed.tech/tags/cloud-apis.md>), [cloud-monitoring](<https://devfeed.tech/tags/cloud-monitoring.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloud-platform](<https://devfeed.tech/tags/cloud-platform.md>), [cloud-run](<https://devfeed.tech/tags/cloud-run.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dynatrace](<https://devfeed.tech/tags/dynatrace.md>), [gcp](<https://devfeed.tech/tags/gcp.md>), [google](<https://devfeed.tech/tags/google.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [logs](<https://devfeed.tech/tags/logs.md>), [messages](<https://devfeed.tech/tags/messages.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [observability](<https://devfeed.tech/tags/observability.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [projects](<https://devfeed.tech/tags/projects.md>), [pub-sub](<https://devfeed.tech/tags/pub-sub.md>), [query](<https://devfeed.tech/tags/query.md>), [release](<https://devfeed.tech/tags/release.md>), [risk](<https://devfeed.tech/tags/risk.md>)

### AI overview

The excerpt shows how to find Pub/Sub messages nearing deletion by comparing each subscription's oldest unacknowledged message age with its configured retention. Dynatrace Cloud Platform Monitoring for Google Cloud makes configuration, metrics, logs, and resource relationships available together; DQL can trace dead-letter policies to destination subscriptions, calculate retention usage and deletion deadlines, and sweep connected projects. In the example, 1,932 failed refunds were safely forwarded to a seven-day dead-letter subscription, but its oldest messages would become eligible for deletion before the planned replay. The source recommends replaying before the deadline after checking idempotency, then alerting on retention used rather than queue depth; owner labels can route alerts. It also describes raising retention to buy time (up to 31 days, with extra cost beyond 24 hours). The excerpt notes Cloud Monitoring fixed-age thresholds require separate thresholds for differing retentions, while Dynatrace can read each subscription's configured retention. Log collection requires a Pub/Sub sink and Dataflow job; metrics and topology use Google Cloud APIs.

### Source excerpt

Google Cloud observability is now generally available for Dynatrace Clouds. With this release, Dynatrace extends its Cloud Observability experience to Google Cloud, bringing resource configuration, metrics, and logs into the same investigation context. You can analyze that context with Dynatrace Query Language (DQL) and use existing cloud labels to route alerts to resource owners. To [...] The post How to find at-risk Pub/Sub messages across Google Cloud projects appeared first on Dynatrace news.

## Sovereign AI is about control, not just location

DevFeed: [Sovereign AI is about control, not just location](<https://devfeed.tech/articles/sovereign-ai-is-about-control-not-just-location-143168.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4250239/sovereign-ai-is-about-control-not-just-location.html>)

Author: Zeus Kerravala

Published: 2026-11-19T08:00:00Z

Content type: news

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [Sovereign AI](<https://devfeed.tech/topics/sovereign-ai.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [big-ip](<https://devfeed.tech/tags/big-ip.md>), [big-ip-next-for-kubernetes](<https://devfeed.tech/tags/big-ip-next-for-kubernetes.md>), [bluefield-3](<https://devfeed.tech/tags/bluefield-3.md>), [control](<https://devfeed.tech/tags/control.md>), [deal](<https://devfeed.tech/tags/deal.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [f5](<https://devfeed.tech/tags/f5.md>), [governance](<https://devfeed.tech/tags/governance.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [high-performance](<https://devfeed.tech/tags/high-performance.md>), [industry](<https://devfeed.tech/tags/industry.md>), [industry-markets-network-security-networking-security-telecommunications-industry](<https://devfeed.tech/tags/industry-markets-network-security-networking-security-telecommunications-industry.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [location](<https://devfeed.tech/tags/location.md>), [markets](<https://devfeed.tech/tags/markets.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [networking](<https://devfeed.tech/tags/networking.md>), [norwegian](<https://devfeed.tech/tags/norwegian.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [security](<https://devfeed.tech/tags/security.md>), [sovereign-ai](<https://devfeed.tech/tags/sovereign-ai.md>), [storytype-analysis](<https://devfeed.tech/tags/storytype-analysis.md>), [telecommunications-industry](<https://devfeed.tech/tags/telecommunications-industry.md>)

### AI overview

The Telenor AI Factory deployment pairs F5 BIG-IP Next for Kubernetes with Nvidia BlueField-3 DPUs to provide an AI service plane for sovereign AI services. Its current controls include tenant isolation, policy-based traffic control, and telemetry for audits and compliance; token-aware governance, circuit breaking, and inference-aware traffic optimization are planned as services scale. The article frames sovereignty as control and auditability over data and workloads, beyond keeping GPUs in-country. It argues telcos could monetize AI by metering and governing tokens, while an AI-aware data path can help allocate GPU capacity efficiently. F5 supplies granular records for billing systems but not billing itself. The Telenor deployment is described as small, and much of its token governance remains planned.

### Source excerpt

Every year at MWC and other telco-related shows, I hear the same line. A new technology wave will finally let telcos create new revenue-generating services. Cloud, virtualization, software, and a number of other trends were the magic elixir that would help telcos be more than just pipes. Every year, most of them use the technology to cut costs while continuing to sell connectivity. The industry has spent two decades trying to avoid becoming a "dumb pipe," and for the most part, it has failed. AI could be the thing that breaks the pattern, but only for operators who understand what they're selling. A recent announcement from F5 and Telenor ASA offers a glimpse of what that could look like. The news Recently, F5 announced that Telenor AI Factory selected BIG-IP Next for Kubernetes, running on Nvidia BlueField-3 data processing units, as the AI service plane for its Nvidia-powered sovereign AI infrastructure. The platform is designed for Norwegian and European organizations seeking high-performance AI services while maintaining control over where data is processed, stored, and accessed. From the outset, F5 provides multitenancy and isolation, policy-based traffic control, and real-time telemetry for auditing and compliance. Telenor also plans to add token-aware governance, circuit breaking, and inference-aware traffic optimization as its commercial AI services scale. I recently spoke with Ahmed Guetari, senior vice president and general manager of F5's service provider business, about the deal and its implications for telcos more broadly. Sovereignty is a control problem Most of the conversation about sovereign AI centers on GPUs located on national soil. That's obviously important, but it's table stakes. A rack of GPUs in Oslo doesn't make an AI service sovereign if the operator can't prove which tenant accessed what data, which model was called, and where the traffic went. Guetari was open about the term itself being fuzzy. "Sovereignty is very vague and not always c

## From Ambiguous Tickets to Ranked Hypotheses: Multi-Agent Root-Cause Analysis for Autonomous Heavy-Vehicle Software

DevFeed: [From Ambiguous Tickets to Ranked Hypotheses: Multi-Agent Root-Cause Analysis for Autonomous Heavy-Vehicle Software](<https://devfeed.tech/articles/from-ambiguous-tickets-to-ranked-hypotheses-multi-agent-root-cause-analysis-for-autonomous-heavy-vehicle-software-142159.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23294>)

Author: Marten Seegers, Maximilian Kneissl, Enrique Aguayo-Lara, Chih-Hong Cheng

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [Parallel reasoning](<https://devfeed.tech/topics/parallel-reasoning.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [autonomous](<https://devfeed.tech/tags/autonomous.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

The workflow turns sparse incident tickets and large vehicle recordings into telemetry-grounded event chains, ranked causal hypotheses, and candidate code locations. Non-neural tools select telemetry once, then an LLM creates shared evidence artifacts, cutting per-incident cost by more than half versus per-analyst querying. Specialist agents independently use fault tree analysis, Kepner-Tregoe analysis, and call-chain tracing; hypotheses reached by multiple analysts rank higher. A separate analyst session examines any suspected ticket cause to reduce anchoring risk. On 12 held-out incidents, the workflow found the faulty file in 10 cases versus 8 for a single agent using the same model and tools, at higher cost. Two domain experts accepted a top-three hypothesis in 4 and 9 cases, respectively, while two LLM judges did not resolve the disagreement, underscoring the difficulty of evaluating causal explanations.

### Source excerpt

arXiv:2611.23294v1 Announce Type: new Abstract: Autonomous haulage systems run safety-critical software on driverless mining trucks, with no onboard driver to detect or mitigate abnormal behavior. Every failure in testing or operation must therefore be traced to its root cause to keep the safety case valid and limit downtime. An investigation often starts from a sparse ticket containing an approximate timestamp, sometimes a suspected cause, and a multimodal vehicle recording of several gigabytes. We present a multi-agent root-cause analysis (RCA) workflow that turns this input into a telemetry-grounded event chain, ranked causal hypotheses, and candidate code locations. A suspected cause in the ticket, which could anchor the analysis on a false theory, goes to a single LLM analyst in a separate agent session. Non-neural tools select the relevant telemetry once, before analysis, and an LLM condenses it into shared evidence artifacts; this more than halved the cost per incident compared with per-analyst querying. Specialist analyst agents then apply established RCA techniques in parallel, including fault tree analysis, Kepner-Tregoe analysis, and call-chain tracing, and hypotheses that several LLM analysts reach independently rank higher. We evaluated the workflow on 12 held-out industrial incidents against a single agent with the same model and tools. It located the faulty file more often (10 vs. 8 cases) at higher cost. Two human domain experts accepted a top-three hypothesis in 4 and 9 cases, respectively. The gap, which two LLM judges did not resolve, shows that rating causal explanations is itself a hard evaluation problem.

## Why Groundcover's CEO says agents are the power users of observability

DevFeed: [Why Groundcover's CEO says agents are the power users of observability](<https://devfeed.tech/articles/why-groundcover-s-ceo-says-agents-are-the-power-users-of-observability-142011.md>)

Original publisher: [Read original article](<https://thenewstack.io/groundcover-coding-agents-observability/>)

Author: Chris J. Preimesberger

Published: 2026-11-19T03:15:24Z

Content type: article

Language: en

Sources: [Kubernetes Overview, News and Trends | The New Stack](<https://devfeed.tech/sources/kubernetes-overview-news-and-trends-the-new-stack.md>), [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [kubecon-cloudnativecon-na-2026](<https://devfeed.tech/tags/kubecon-cloudnativecon-na-2026.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [observability](<https://devfeed.tech/tags/observability.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [power-users](<https://devfeed.tech/tags/power-users.md>), [sponsor-groundcover](<https://devfeed.tech/tags/sponsor-groundcover.md>), [sponsored](<https://devfeed.tech/tags/sponsored.md>), [sponsored-podcast](<https://devfeed.tech/tags/sponsored-podcast.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Groundcover exposes production telemetry to coding agents through MCP, so they can use traces to investigate latency and observed behavior to guide tests; its own agents also use telemetry from staging in code reviews. The article describes agent runs as potentially lasting hours and spanning thousands of tool calls, making prompts, tool calls, and evaluations useful for understanding behavior beyond whether a run completed. Groundcover collects application and infrastructure signals with an eBPF sensor without requiring an SDK for every service, while supporting OpenTelemetry and custom instrumentation for more detail. Its bring-your-own-cloud model keeps telemetry and Groundcover's agent operations in the customer's cloud; customers pay for the infrastructure and Groundcover manages deployment. The CEO describes Kubernetes cost and resilience optimization as current work and agent-led incident response across code and infrastructure as a possible next step.

### Source excerpt

An AI coding agent can write a patch in minutes. Ask it whether that patch slows down the API endpoint The post Why Groundcover's CEO says agents are the power users of observability appeared first on The New Stack.

## Elastic and HoneyHive join forces to advance AI observability and evaluation

DevFeed: [Elastic and HoneyHive join forces to advance AI observability and evaluation](<https://devfeed.tech/articles/elastic-and-honeyhive-join-forces-to-advance-ai-observability-and-evaluation-146502.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/elastic-and-honeyhive>)

Author: Santosh Krishnan

Published: 2026-11-19T00:00:00Z

Content type: news

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [observability](<https://devfeed.tech/topics/observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-behavior](<https://devfeed.tech/tags/agent-behavior.md>), [agent-workflows](<https://devfeed.tech/tags/agent-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-observability](<https://devfeed.tech/tags/ai-observability.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [announce](<https://devfeed.tech/tags/announce.md>), [application-monitoring](<https://devfeed.tech/tags/application-monitoring.md>), [applications](<https://devfeed.tech/tags/applications.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [data](<https://devfeed.tech/tags/data.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [observability](<https://devfeed.tech/tags/observability.md>), [reliable-ai-agents](<https://devfeed.tech/tags/reliable-ai-agents.md>)

### AI overview

Elastic has entered into an agreement to acquire HoneyHive, an enterprise AI observability and evaluation platform. HoneyHive traces complex agent workflows and supports offline evaluation and experimentation before deployment, plus ongoing production monitoring and evaluation to identify unexpected behavior and guide improvements. The announcement distinguishes this agent-focused view of behavior and outcomes from traditional monitoring of application performance. Elastic aims to integrate HoneyHive's tracing and evaluation with its search and analytics foundation, linking agent quality to broader operational context. Existing HoneyHive customers are intended to remain supported during integration; a consolidated product roadmap is expected in coming months.

### Source excerpt

Today, we're taking a meaningful step toward helping customers build more reliable AI agents and applications. We're excited to announce that Elastic has entered into an agreement to acquire HoneyHive.

## Long-term Amazon Redshift observability with Datadog and Amazon S3 Tables

DevFeed: [Long-term Amazon Redshift observability with Datadog and Amazon S3 Tables](<https://devfeed.tech/articles/long-term-amazon-redshift-observability-with-datadog-and-amazon-s3-tables-141880.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/long-term-amazon-redshift-observability-with-datadog-and-amazon-s3-tables/>)

Author: Raghu Kuppala

Published: 2026-11-18T22:57:27Z

Content type: tutorial

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Apache Iceberg](<https://devfeed.tech/topics/apache-iceberg.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [elt](<https://devfeed.tech/topics/elt.md>)

Tags: [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-s3-tables](<https://devfeed.tech/tags/amazon-s3-tables.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apache-airflow](<https://devfeed.tech/tags/apache-airflow.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-iceberg-tables](<https://devfeed.tech/tags/apache-iceberg-tables.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service-aws-kms](<https://devfeed.tech/tags/aws-key-management-service-aws-kms.md>), [data-observability](<https://devfeed.tech/tags/data-observability.md>), [data-quality](<https://devfeed.tech/tags/data-quality.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [history](<https://devfeed.tech/tags/history.md>), [integration](<https://devfeed.tech/tags/integration.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [query](<https://devfeed.tech/tags/query.md>)

### AI overview

Amazon Redshift system tables retain history for only 7 days. The S3 Tables integration continuously exports selected system table data as Apache Iceberg tables, letting customers set retention and query the history without collection queries consuming warehouse compute. Datadog Data Observability can read that history to build column-level lineage, normalized query profiles, and context for quality alerts across connected clusters and workgroups. It still connects to Redshift for metadata and runs configured aggregate quality monitors there. Setup requires enabling per-warehouse exports, integrating S3 Tables with the AWS Glue Data Catalog, and granting the Datadog IAM role read access; the feature is described as a preview requiring account-team access. Disabling exports creates a history gap that cannot be backfilled after Redshift's 7-day window, and customer-managed KMS encryption keys cannot be changed after table creation.

### Source excerpt

Amazon Redshift keeps only 7 days of system table history. This post pairs Datadog Data Observability with the new Amazon Redshift system table integration with Amazon S3 Tables, so you can retain query history for the long term and analyze lineage, query performance, and data quality without adding load to your warehouses.

## Thoughts on Verification Engineering in the Agentic SDLC

DevFeed: [Thoughts on Verification Engineering in the Agentic SDLC](<https://devfeed.tech/articles/thoughts-on-verification-engineering-in-the-agentic-sdlc-142073.md>)

Original publisher: [Read original article](<https://www.dataengineeringweekly.com/p/thoughts-on-verification-engineering>)

Author: Ananth Packkildurai

Published: 2026-11-18T21:59:55Z

Content type: article

Language: en

Sources: [Data Engineering Weekly](<https://devfeed.tech/sources/data-engineering-weekly.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-sdlc](<https://devfeed.tech/tags/agentic-sdlc.md>), [agentic-software](<https://devfeed.tech/tags/agentic-software.md>), [agentic-software-development](<https://devfeed.tech/tags/agentic-software-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [code](<https://devfeed.tech/tags/code.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [manufacturing](<https://devfeed.tech/tags/manufacturing.md>), [sdlc](<https://devfeed.tech/tags/sdlc.md>), [software](<https://devfeed.tech/tags/software.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The article argues that AI accelerates code production faster than existing review and testing loops can verify it, shifting the engineering bottleneck toward proving behavior before release. Static analysis and human diff reviews may miss cross-service runtime failures, while relying on canaries risks exposing users to too many regressions. It proposes Verification Engineering built around disposable production-equivalent sandboxes, synthetic test data shaped by domain distributions and failure patterns, automatically generated test harnesses and correctness/performance/resource assertions, and simulated end-to-end user workflows. Requirements and designs would become executable specifications, while production logs, traces, and interactions would feed anomalies back into future sandbox tests. These are presented as a proposed discipline, not as a comparison of specific products or evidence of measured results.

### Source excerpt

When AI accelerates code manufacturing, the software supply chain bottleneck shifts from writing code to building the feedback loop that proves it works.

## Scripts can't run AI factories: Dell moves cluster management from the server to the rack

DevFeed: [Scripts can't run AI factories: Dell moves cluster management from the server to the rack](<https://devfeed.tech/articles/scripts-can-t-run-ai-factories-dell-moves-cluster-management-from-the-server-to-the-rack-140317.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/18/supercomputing-needs-rack-scale-management-dell-says-dellatsc26/>)

Author: Jonathan Anthony

Published: 2026-11-18T10:46:31Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [dell](<https://devfeed.tech/topics/dell.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [accelerated-computing](<https://devfeed.tech/tags/accelerated-computing.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-data-centers](<https://devfeed.tech/tags/ai-data-centers.md>), [ai-factories](<https://devfeed.tech/tags/ai-factories.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-supercomputers](<https://devfeed.tech/tags/ai-supercomputers.md>), [amd](<https://devfeed.tech/tags/amd.md>), [andrew-vaz](<https://devfeed.tech/tags/andrew-vaz.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [cluster-management](<https://devfeed.tech/tags/cluster-management.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [dell](<https://devfeed.tech/tags/dell.md>), [dell-fabric-manager](<https://devfeed.tech/tags/dell-fabric-manager.md>), [dell-openmanage-rack-scale](<https://devfeed.tech/tags/dell-openmanage-rack-scale.md>), [dellatsc26](<https://devfeed.tech/tags/dellatsc26.md>), [energy-efficiency](<https://devfeed.tech/tags/energy-efficiency.md>), [gemma-allen](<https://devfeed.tech/tags/gemma-allen.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [high-performance-computing](<https://devfeed.tech/tags/high-performance-computing.md>), [hpc](<https://devfeed.tech/tags/hpc.md>), [idrac](<https://devfeed.tech/tags/idrac.md>), [infra](<https://devfeed.tech/tags/infra.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [john-furrier](<https://devfeed.tech/tags/john-furrier.md>), [meta](<https://devfeed.tech/tags/meta.md>), [news](<https://devfeed.tech/tags/news.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [nvl72](<https://devfeed.tech/tags/nvl72.md>), [openmanage-enterprise](<https://devfeed.tech/tags/openmanage-enterprise.md>), [rack](<https://devfeed.tech/tags/rack.md>), [saurabh-kapoor](<https://devfeed.tech/tags/saurabh-kapoor.md>), [sc26](<https://devfeed.tech/tags/sc26.md>), [sc26eventpage](<https://devfeed.tech/tags/sc26eventpage.md>), [supercomputing](<https://devfeed.tech/tags/supercomputing.md>), [thecube](<https://devfeed.tech/tags/thecube.md>)

### AI overview

Dell says AI clusters have become too complex to manage with manual scripts, shifting infrastructure operations from individual servers to whole racks. At SC26, it introduced OpenManage Rack Scale, which manages up to 100,000 devices in its first release, compared with 8,000 servers for OpenManage Enterprise, and Fabric Manager, which turns validated Nvidia and AMD designs into deployable blueprints across network operating systems and silicon. Dell also cites iDRAC telemetry exceeding 320 metrics per server and a local-LLM chatbot for querying it. The article highlights cooling risks, hard-to-diagnose component failures and surging network traffic as reasons to correlate telemetry across systems; it provides no independent performance evaluation of the tools.

### Source excerpt

As artificial intelligence clusters grow to supercomputing scale, the hard part of the AI factory is no longer buying hardware. It is keeping racks, switches, GPUs and cooling running once they are switched on. That operational burden is reshaping what infrastructure providers sell. Dell Technologies Inc. has spent the past year pushing its AI Factory [...] The post Scripts can't run AI factories: Dell moves cluster management from the server to the rack appeared first on SiliconANGLE.

## Microsoft announces Windows Server 2028 with hardened security

DevFeed: [Microsoft announces Windows Server 2028 with hardened security](<https://devfeed.tech/articles/microsoft-announces-windows-server-2028-with-hardened-security-140170.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/microsoft/microsoft-announces-windows-server-2028-with-hardened-security/>)

Author: Sergiu Gatlan

Published: 2026-11-18T09:24:31Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Windows](<https://devfeed.tech/topics/windows.md>), [systems](<https://devfeed.tech/topics/systems.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [kerberos](<https://devfeed.tech/topics/kerberos.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [accelerators](<https://devfeed.tech/tags/accelerators.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-accelerators](<https://devfeed.tech/tags/ai-accelerators.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computers](<https://devfeed.tech/tags/computers.md>), [confidential-vm](<https://devfeed.tech/tags/confidential-vm.md>), [enterprise-infrastructure](<https://devfeed.tech/tags/enterprise-infrastructure.md>), [ignite](<https://devfeed.tech/tags/ignite.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>), [windows-insider](<https://devfeed.tech/tags/windows-insider.md>), [windows-server](<https://devfeed.tech/tags/windows-server.md>), [windows-server-2028](<https://devfeed.tech/tags/windows-server-2028.md>)

### AI overview

Windows Server 2028 is announced with hardened Server Core settings enabled by default, covering identity, network exposure, cryptography, administration, code integrity, remote access, and auditing. Admins can relax specific settings through a new security baseline. The article says Trusted Launch protects VM boot integrity and Confidential VM support is beginning on supported hardware. Some planned hardening, including NTLM blocking and hardware-backed platform protection, is still in progress. Other announced changes include Intune management for eligible persistent servers, native NVMe and NVMe over TCP/RDMA support, ReFS boot, and tools for deploying inference environments and managing accelerated hardware and models. Testing is available through the Windows Insider Program or an application to the Server Technology Adoption Program.

### Source excerpt

Microsoft has announced Windows Server 2028, the next major release of its server operating system, at the Ignite 2026 conference on Tuesday. [...]

## Is your observability pipeline becoming the bottleneck?

DevFeed: [Is your observability pipeline becoming the bottleneck?](<https://devfeed.tech/articles/is-your-observability-pipeline-becoming-the-bottleneck-140944.md>)

Original publisher: [Read original article](<https://www.confluent.io/blog/is-your-observability-pipeline-becoming-the-bottleneck/>)

Author: Confluent Staff

Published: 2026-11-18T05:04:51Z

Content type: article

Language: en

Sources: [Confluent: Data in motion](<https://devfeed.tech/sources/confluent-data-in-motion.md>)

Topics: [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [data-streaming](<https://devfeed.tech/tags/data-streaming.md>), [guide](<https://devfeed.tech/tags/guide.md>), [limits](<https://devfeed.tech/tags/limits.md>), [observability](<https://devfeed.tech/tags/observability.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>)

### AI overview

Telemetry spikes can expose observability pipeline limits: downstream systems may delay or drop events just when engineers need them, while rising volumes can increase ingestion costs, complicate adding destinations, and leave engineers maintaining scripts and integrations. The excerpt identifies these four patterns as signs to reassess filtering, processing, and data flow. A streaming layer between collection and destinations may help in some environments, but adds operational responsibilities and cost; whether it is worthwhile depends on the benefits and the technical requirements of the specific environment. The referenced guide explores those requirements and where IBM Confluent Data Streaming Platform may fit.

### Source excerpt

Discover four signs your observability pipeline is reaching its limits and learn how data streaming can help you build a more scalable architecture. Get the guide.

## Where Root Cause Analysis Fails: A Retrieval-Reranking Decomposition

DevFeed: [Where Root Cause Analysis Fails: A Retrieval-Reranking Decomposition](<https://devfeed.tech/articles/where-root-cause-analysis-fails-a-retrieval-reranking-decomposition-141609.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2609.36686>)

Author: Hada Melino Muhammad, Luan Pham, Laure Barri\\\`ere, Sachin Shetty, Leonardo Pulga, Flora D. Salim

Published: 2026-11-18T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [observability](<https://devfeed.tech/topics/observability.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [benchmark overfitting machine learning](<https://devfeed.tech/topics/benchmark-overfitting-machine-learning.md>)

Tags: [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [reranking](<https://devfeed.tech/tags/reranking.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>)

### AI overview

The paper argues that top@k accuracy hides whether root cause analysis fails to retrieve the true cause or retrieves it but ranks it too low. On industrial CPS benchmarks, statistical scoring mis-ranks the cause 79-100% of the time, while graph-based methods do not clearly outperform the best statistical baseline. On microservice benchmarks, retrieval reaches 98-100%, where injected faults sharply raise the faulty service's own metric. A two-stage multi-signal retriever and LLM reranker, requiring neither causal graphs nor labeled data, matches or exceeds baseline top@1 accuracy across six benchmark suites by up to 12 points. When the cause is guaranteed among candidates, adding a short system description improves the reranker's lead over the best baseline to 7-18 points across benchmarks.

### Source excerpt

arXiv:2609.36686v2 Announce Type: replace Abstract: Identifying the root cause of an anomaly among hundreds of sensors is critical for preventing safety incidents and costly downtime in complex monitored systems. Existing studies evaluate root cause analysis (RCA) methods using top@k accuracy. We show that this metric has a fundamental blind spot: it conflates two failure modes, retrieval failure, where the true cause is never considered, and reranking failure, where it is considered but ranked too low. In this work, we introduce a retrieval-reranking decomposition and audit four well-known benchmarks to expose this blind spot. Our experiments show that, on industrial CPS benchmarks, the statistical baseline scoring every sensor mis-ranks the true cause 79-100% of the time, and graph-based methods never clearly beat the best statistical baseline, whether their causal graphs are learned on short fault windows, on retrieved candidate pools guaranteed to contain the cause, or on multi-day normal-operation data. Meanwhile, on microservice benchmarks, where each injected fault drives the faulty service's own metric far above its baseline, retrieval is nearly solved (98-100%). Guided by the decomposition, we build a two-stage pipeline combining a multi-signal retriever with an LLM reranker that, as one fixed configuration, matches or exceeds the best baseline's top@1 accuracy on all six benchmark suites (by up to +12 points), with no causal graph or labeled data required. When all methods rank the same retrieved candidates with the true cause guaranteed present, adding a short system-description document lets the reranker lead the best baseline by +7 to +18 points on every benchmark. Code is available at https://github.com/cruiseresearchgroup/DecompRCA.

## How we raised Databricks cluster rate limits by 7.5x

DevFeed: [How we raised Databricks cluster rate limits by 7.5x](<https://devfeed.tech/articles/how-we-raised-databricks-cluster-rate-limits-by-7-5-139643.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-we-raised-databricks-cluster-rate-limits-75>)

Author: Heqing Ya; Tan Zhang; Ankit Batra; Abhishek Rai

Published: 2026-11-18T02:30:31Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [aggregate](<https://devfeed.tech/tags/aggregate.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-platform](<https://devfeed.tech/tags/compute-platform.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [limits](<https://devfeed.tech/tags/limits.md>), [platform](<https://devfeed.tech/tags/platform.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Databricks raised default cluster-creation request-rate limits 7.5x by adding adaptive concurrency control for the longer provisioning workflows behind each API call. Each active workflow holds a slot through VM provisioning and dependency waits; health signals such as provisioning latency and thread-pool saturation guide the slot limit. When capacity falls, accepted requests queue and start more slowly; as conditions recover, concurrency increases cautiously. The fixed API rate limit remains a guardrail for exceptionally high traffic. This separates capacity management from request-rate enforcement, but a successful API response does not promise an immediate launch or fixed completion time. Queues need bounded size and wait times, and retries need backoff and attempt limits; concurrency limits cannot restore an unavailable dependency. The reported rollout raised default limits 7.5x, reduced cluster-creation rate-limit errors by more than 99.99% in the stated scope, and removed over a hundred customer-specific overrides in scope. Since the increase, few customers have hit the higher limits and no new manual overrides have been added.

### Source excerpt

As part of the Compute Platform team at Databricks, we turn cloud infrastructure...

## Explore OpenSearch 3.10

DevFeed: [Explore OpenSearch 3.10](<https://devfeed.tech/articles/explore-opensearch-3-10-141101.md>)

Original publisher: [Read original article](<https://opensearch.org/blog/explore-opensearch-3-10/>)

Author: James McIntyre

Published: 2026-11-18T01:03:47Z

Content type: release

Language: en

Sources: [OpenSearch](<https://devfeed.tech/sources/opensearch.md>)

Topics: [opensearch](<https://devfeed.tech/topics/opensearch.md>), [hybrid-search](<https://devfeed.tech/topics/hybrid-search.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-tracing](<https://devfeed.tech/tags/agent-tracing.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-tracing](<https://devfeed.tech/tags/ai-agent-tracing.md>), [apis](<https://devfeed.tech/tags/apis.md>), [blog](<https://devfeed.tech/tags/blog.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [fusion](<https://devfeed.tech/tags/fusion.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [keystore](<https://devfeed.tech/tags/keystore.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [opensearch](<https://devfeed.tech/tags/opensearch.md>), [releases](<https://devfeed.tech/tags/releases.md>), [search](<https://devfeed.tech/tags/search.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

### AI overview

OpenSearch 3.10 adds hybrid-query fusion that puts score normalization and combination in the query, supports nesting and per-request weights, and retains rescoring, explanations, and pagination. Experimental agentic search templates constrain the LLM to selecting a registered template and filling parameters. Observability adds service dependencies and multi-turn agent traces, while PPL gains time-range index pruning, streaming results, and cross-cluster queries. Pull-based ingestion can read uncompressed, append-only NDJSON from object storage with stable document IDs. Security adds atomic bulk access-control updates and keystore-based token keys. Workload throttling offers low-latency per-node limits or coordinated cluster-wide limits with added latency; request queueing is planned for a future release. Some observability features require the separately versioned Observability Stack with Data Prepper 2.17.

### Source excerpt

OpenSearch 3.10 introduces hybrid search fusion mode, experimental agentic search templates, AI agent tracing, pull-based ingestion from object storage, and new security features including bulk role APIs and keystore-based on-behalf-of token keys. The post Explore OpenSearch 3.10 appeared first on OpenSearch.

## Why the Holidays are Gaming's Biggest Season and Its Riskiest

DevFeed: [Why the Holidays are Gaming's Biggest Season and Its Riskiest](<https://devfeed.tech/articles/why-the-holidays-are-gaming-s-biggest-season-and-its-riskiest-143979.md>)

Original publisher: [Read original article](<https://www.fastly.com/blog/why-holidays-are-gamings-biggest-season-and-riskiest/>)

Author: Ashley Hurwitz

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Fastly Blog](<https://devfeed.tech/sources/fastly-blog.md>)

Topics: [observability in gaming](<https://devfeed.tech/topics/observability-in-gaming.md>), [observability](<https://devfeed.tech/topics/observability.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [apis](<https://devfeed.tech/tags/apis.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bot-detection](<https://devfeed.tech/tags/bot-detection.md>), [bot-protection](<https://devfeed.tech/tags/bot-protection.md>), [bots](<https://devfeed.tech/tags/bots.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [credential-stuffing](<https://devfeed.tech/tags/credential-stuffing.md>), [ddos](<https://devfeed.tech/tags/ddos.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-cloud](<https://devfeed.tech/tags/edge-cloud.md>), [fastly](<https://devfeed.tech/tags/fastly.md>), [fraud](<https://devfeed.tech/tags/fraud.md>), [fraud-prevention](<https://devfeed.tech/tags/fraud-prevention.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [holidays](<https://devfeed.tech/tags/holidays.md>), [industry-insights](<https://devfeed.tech/tags/industry-insights.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Holiday gaming traffic surges can conceal credential stuffing, account takeover, gift card fraud, or DDoS activity, while capacity failures and attacks may look alike. The excerpt says attackers target gaming APIs as well as web portals, and that peak volumes make threats harder to distinguish. It recommends absorbing surges with edge load balancing, correlating real-time logs with availability and login signals, rate limiting requests before they reach origin, and using automated bot detection and edge WAF rules. These controls need to distinguish players from bots: overly rigid rules can block legitimate logins or registrations. The described goal is to keep the platform available and catch attacks without slowing or locking out players.

### Source excerpt

Holiday traffic surges in gaming hide the attacks riding along with them. Learn how to protect capacity and catch credential stuffing without slowing down players.

## Building a reliable AI agent with OSCAR

DevFeed: [Building a reliable AI agent with OSCAR](<https://devfeed.tech/articles/building-a-reliable-ai-agent-with-oscar-141983.md>)

Original publisher: [Read original article](<https://temporal.io/blog/building-a-reliable-ai-agent-with-oscar>)

Author: Loïc Ortola

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [Temporal](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Spring AI](<https://devfeed.tech/topics/spring-ai.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-framework](<https://devfeed.tech/tags/agent-framework.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-loop](<https://devfeed.tech/tags/agentic-loop.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-decisions](<https://devfeed.tech/tags/ai-decisions.md>), [building](<https://devfeed.tech/tags/building.md>), [community](<https://devfeed.tech/tags/community.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [retries](<https://devfeed.tech/tags/retries.md>), [spring](<https://devfeed.tech/tags/spring.md>), [spring-ai](<https://devfeed.tech/tags/spring-ai.md>), [temporal](<https://devfeed.tech/tags/temporal.md>)

### AI overview

OSCAR turns an emailed refund request into an action across the marketplace backend and Stripe, using an LLM to interpret the complaint and tools to check orders, update status, issue refunds, and reply. The initial Spring AI prototype can complete the flow, but a Stripe outage or process restart can leave partial work stranded, with no recovery or visibility into the agent's decisions. The Spring AI/Temporal integration runs model calls and external tools as Activities, adding retries and durable resumption while preserving the agent's business logic; Temporal's UI records inputs, results, retries, and failures, though individual retry attempts need Worker logs or extra instrumentation. Workflows can also pause without polling for human approval, resume after a process restart, and branch on the decision or a timeout. Temporal does not solve context growth, prompt or tool quality, or security: backend tools must independently validate and authorize actions, since agent instructions are not a security boundary.

### Source excerpt

Learn how to take a Spring AI agent from prototype to production with Temporal, adding durable execution, retries, observability, and human approval.

## Apple outage: iPhone apps suffer disruption days after major Microsoft issues

DevFeed: [Apple outage: iPhone apps suffer disruption days after major Microsoft issues](<https://devfeed.tech/articles/apple-outage-iphone-apps-suffer-disruption-days-after-major-microsoft-issues-139727.md>)

Original publisher: [Read original article](<https://www.theguardian.com/technology/2026/nov/17/gmail-apple-outage-major-disruption>)

Author: Anna Betts and Blake Montgomery

Published: 2026-11-17T22:23:56Z

Content type: news

Language: en

Sources: [The Guardian | Technology](<https://devfeed.tech/sources/the-guardian-technology.md>)

Topics: [Resilience](<https://devfeed.tech/topics/resilience.md>), [iphone](<https://devfeed.tech/topics/iphone.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [app-store](<https://devfeed.tech/tags/app-store.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apple-outage](<https://devfeed.tech/tags/apple-outage.md>), [apple-pay](<https://devfeed.tech/tags/apple-pay.md>), [apple-technology-computing](<https://devfeed.tech/tags/apple-technology-computing.md>), [applecare](<https://devfeed.tech/tags/applecare.md>), [apps](<https://devfeed.tech/tags/apps.md>), [computing](<https://devfeed.tech/tags/computing.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [downdetector](<https://devfeed.tech/tags/downdetector.md>), [gmail](<https://devfeed.tech/tags/gmail.md>), [google](<https://devfeed.tech/tags/google.md>), [google-s](<https://devfeed.tech/tags/google-s.md>), [icloud](<https://devfeed.tech/tags/icloud.md>), [icloud-mail](<https://devfeed.tech/tags/icloud-mail.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [mail](<https://devfeed.tech/tags/mail.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [outage](<https://devfeed.tech/tags/outage.md>), [outages](<https://devfeed.tech/tags/outages.md>), [problems](<https://devfeed.tech/tags/problems.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

Thousands reported disruptions to Apple services and Gmail on Tuesday. Apple said an internal update caused outages and that many systems were restored while it worked to bring the remaining systems back online; its status page listed issues including the App Store and iCloud services. Google said it saw no evidence of a broad Gmail disruption and directed users to its Workspace Status Dashboard for status updates. The reports followed other service interruptions, but the excerpt does not establish a common cause across them.

### Source excerpt

Google's Gmail also affected after problems reported in technological infrastructure in the US and worldwide Thousands reported disruptions to Google's Gmail and Apple's iPhone apps, such as Apple Pay and iCloud, on Tuesday, according to Downdetector. Apple confirmed the outages in a statement but said it had resolved them, while Google said it had not seen internal signs of outages. Apple's own system status page as of 2.30pmET showed problems with services such as the App Store, iCloud Mail, iCloud Web Apps and AppleCare. Continue reading...

## Vercel Blob now supports TTLs for automatic deletion

DevFeed: [Vercel Blob now supports TTLs for automatic deletion](<https://devfeed.tech/articles/vercel-blob-now-supports-ttls-for-automatic-deletion-138555.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-blob-now-supports-ttls-for-automatic-deletion>)

Author: Agustin Falco

Published: 2026-11-17T18:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [CRUD](<https://devfeed.tech/topics/crud.md>), [observability](<https://devfeed.tech/topics/observability.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [2-9-0](<https://devfeed.tech/tags/2-9-0.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [blob](<https://devfeed.tech/tags/blob.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cli](<https://devfeed.tech/tags/cli.md>), [copy](<https://devfeed.tech/tags/copy.md>), [costs](<https://devfeed.tech/tags/costs.md>), [existing](<https://devfeed.tech/tags/existing.md>), [free](<https://devfeed.tech/tags/free.md>), [image](<https://devfeed.tech/tags/image.md>), [npm](<https://devfeed.tech/tags/npm.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operations](<https://devfeed.tech/tags/operations.md>), [session](<https://devfeed.tech/tags/session.md>), [tab](<https://devfeed.tech/tags/tab.md>), [time](<https://devfeed.tech/tags/time.md>), [ttl](<https://devfeed.tech/tags/ttl.md>), [upload](<https://devfeed.tech/tags/upload.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [works](<https://devfeed.tech/tags/works.md>)

### AI overview

Vercel Blob can automatically delete blobs 1-730 days after upload using `ttlDays`, supported by `put()`, `copy()`, `putImage()`, multipart uploads, and presigned upload URLs. Write results and `head()` responses include `expiresAt`. `setTtl()` can change or clear TTLs on existing blobs, for up to 1,000 URLs at a time, without re-uploading. Vercel CLI 65.16.0 and later supports `--ttl-days` and `vercel blob set-ttl`. Setting a TTL costs one Advanced Operation per started 60 days in addition to the write: 7 days costs one and 730 days costs 13. Clearing TTLs and automatic deletions are free; TTL operations appear in Blob Observability.

### Source excerpt

Vercel Blob can now delete blobs automatically. Pass ttlDays when you write a blob and it is deleted that many days after upload, from 1 to 730 days. The TTL counts from the blob's upload date. Use TTLs for blobs you would otherwise delete yourself, such as session transcripts, exports, and temporary uploads. ttlDays works on put(), copy(), putImage(), multipart uploads, and presigned upload URLs. Every write result and head() response now includes expiresAt, so you know when a blob is due for deletion. setTtl() changes or removes the TTL of blobs you already have, one URL or up to 1,000 at a time, without re-uploading them. In Vercel CLI 65.16.0 and later, pass --ttl-days to vercel blob put, put-image, copy or presign, and use vercel blob set-ttl on existing blobs. Setting a TTL costs one Advanced Operation per started 60 days, on top of the write. A 7-day TTL costs one, and the 730-day maximum costs 13. Clearing a TTL and the deletions themselves are free. You can track TTL operations in the Blob section of the Observability tab. npm install @vercel/blob@2.9.0 Learn more in the Vercel Blob documentation. Read more

## The infrastructure behind a technology first, AI-ready venue

DevFeed: [The infrastructure behind a technology first, AI-ready venue](<https://devfeed.tech/articles/the-infrastructure-behind-a-technology-first-ai-ready-venue-138075.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/industries/the-infrastructure-behind-a-technology-first-ai-ready-venue>)

Author: Pete DeNitto

Published: 2026-11-17T14:00:35Z

Content type: article

Language: en

Sources: [Cisco Blogs](<https://devfeed.tech/sources/cisco-blogs.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [observability](<https://devfeed.tech/topics/observability.md>), [it modernization](<https://devfeed.tech/topics/it-modernization.md>), [Nexus Dashboard](<https://devfeed.tech/topics/nexus-dashboard.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-ready-infrastructure](<https://devfeed.tech/tags/ai-ready-infrastructure.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-catalyst-center](<https://devfeed.tech/tags/cisco-catalyst-center.md>), [compute](<https://devfeed.tech/tags/compute.md>), [industries](<https://devfeed.tech/tags/industries.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [networking](<https://devfeed.tech/tags/networking.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operations](<https://devfeed.tech/tags/operations.md>), [platform](<https://devfeed.tech/tags/platform.md>), [splunk](<https://devfeed.tech/tags/splunk.md>), [sports-media-entertainment](<https://devfeed.tech/tags/sports-media-entertainment.md>)

### AI overview

Monumental Sports & Entertainment replaced Capital One Arena's fragmented, aging systems with an integrated Cisco foundation spanning networking, compute, and observability. Cisco Wi-Fi 7, extensive fiber, and 6 GHz spectrum support venue connectivity and internal operations; a data center with 1.2 Tbps aggregate backplane capacity supports in-house production, 4K video delivery, and future AI workloads. Operations are coordinated through Catalyst Center for campus network health, Splunk Cloud Platform for correlated logs and troubleshooting context, and Intersight for compute health and resource visibility. The team reports that a process that once took 20-30 minutes across disconnected tools now provides a unified view of failures and affected users, helping it isolate problems faster. AI applications such as attendee engagement and predictive analytics are described as planned or enabled by the foundation, not established outcomes.

### Source excerpt

Monumental Sports & Entertainment unified networking, compute, and observability on one Cisco platform. Discover how this AI-ready foundation simplifies IT operations and elevates the fan experience at Capital One Arena.

## Is your OpenTelemetry pipeline becoming a performance bottleneck?

DevFeed: [Is your OpenTelemetry pipeline becoming a performance bottleneck?](<https://devfeed.tech/articles/is-your-opentelemetry-pipeline-becoming-a-performance-bottleneck-140139.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/11/17/is-your-opentelemetry-pipeline-becoming-a-performance-bottleneck/>)

Author: Diana Todea (CNCF Ambassador, OpenTelemetry Documentation approver, Romanian Localization maintainer)

Published: 2026-11-17T12:21:00Z

Content type: article

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [observability](<https://devfeed.tech/topics/observability.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [austria](<https://devfeed.tech/tags/austria.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [building](<https://devfeed.tech/tags/building.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [collecting](<https://devfeed.tech/tags/collecting.md>), [cost](<https://devfeed.tech/tags/cost.md>), [days](<https://devfeed.tech/tags/days.md>), [easy](<https://devfeed.tech/tags/easy.md>), [exploring](<https://devfeed.tech/tags/exploring.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [i](<https://devfeed.tech/tags/i.md>), [native](<https://devfeed.tech/tags/native.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observability-pipelines](<https://devfeed.tech/tags/observability-pipelines.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>)

### AI overview

OpenTelemetry overhead comes from the whole pipeline, from instrumentation and attribute volume to polling, processing, export, and storage; its impact depends on workload, so a single overhead percentage is misleading. The source recommends benchmarking CPU, memory, latency, throughput, telemetry volume, and loss while changing settings individually. Its Collector examples cover exporter batching (which can reduce export work but increase buffering and latency), removing unused resource attributes, lengthening receiver polling intervals where lower time resolution is acceptable, and sampling traces (with tail sampling adding memory and processing costs). It advises placing the memory limiter early for protection under pressure, while noting it can refuse data and does not replace capacity planning. For Kubernetes, it describes separating edge collection from gateway processing, planning queues and retries for outages, and routing each trace to the same instance for tail sampling. Telemetrygen isolates Collector behavior in synthetic experiments; real application instrumentation overhead requires a representative application environment.

### Source excerpt

At Cloud Native Days Austria 2026, I presented a talk called How to Defeat OTel's Silent Killer: The Performance Overhead, exploring a problem that is easy to overlook when building observability pipelines: the cost of collecting...

[Next page](<https://devfeed.tech/topics/observability.md?cursor=WyIyMDI2LTExLTE3VDEyOjIxOjAwKzAwOjAwIiwgImVlNzlhMDU3LWU4YzUtNDMyNC1hOWJlLTg4MDBlYWIwMGRmNSJd>)