# observability pipelines

Observability pipelines are software pipelines that receive, process, and export telemetry such as traces, metrics, and logs to observability backends or other destinations.

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

## MinIO AIStor Memory Reaches GA at SC26 as Datadog Certifies AIStor for On-Premises BYOC Logs

DevFeed: [MinIO AIStor Memory Reaches GA at SC26 as Datadog Certifies AIStor for On-Premises BYOC Logs](<https://devfeed.tech/articles/minio-aistor-memory-reaches-ga-at-sc26-as-datadog-certifies-aistor-for-on-premises-byoc-logs-141144.md>)

Original publisher: [Read original article](<https://www.storagereview.com/news/minio-announces-aistor-memory-is-ga-and-datadog-byoc-lakehouse-certification>)

Author: Harold Fritts

Published: 2026-11-18T14:10:16Z

Content type: news

Language: en

Sources: [StorageReview.com](<https://devfeed.tech/sources/storagereview-com.md>)

Topics: [MinIO](<https://devfeed.tech/topics/minio.md>), [datadog](<https://devfeed.tech/topics/datadog.md>), [archive search](<https://devfeed.tech/topics/archive-search.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-context](<https://devfeed.tech/tags/agent-context.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [layer](<https://devfeed.tech/tags/layer.md>), [logs](<https://devfeed.tech/tags/logs.md>), [memory](<https://devfeed.tech/tags/memory.md>), [minio](<https://devfeed.tech/tags/minio.md>), [minio-aistor](<https://devfeed.tech/tags/minio-aistor.md>), [partnership](<https://devfeed.tech/tags/partnership.md>), [preview](<https://devfeed.tech/tags/preview.md>), [sc26](<https://devfeed.tech/tags/sc26.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [workspaces](<https://devfeed.tech/tags/workspaces.md>)

### AI overview

AIStor Memory is generally available, keeping agents' long-term memory, persistent workspaces, and secrets on enterprise-controlled infrastructure. MinIO says agents can reuse governed knowledge across sessions, but provides no measured quality, latency, or token-cost results. Separately, Datadog has certified AIStor as an on-premises storage foundation for BYOC logs: logs and BYOC indexing and search stay in the customer's environment, and query results reach Datadog over an outbound TLS connection. BYOC currently supports logs; trace and metric support is described as forthcoming. The text does not define what certification tested or provide sizing, ingest-rate, or query-performance data. AIStor Tables can store Iceberg data alongside logs, and MinIO says pricing is based on usable capacity without per-operation or egress charges.

### Source excerpt

MinIO announced the general availability of AIStor Memory today at SC26, moving its agent memory layer out of the technology preview we covered in July. AIStor Memory keeps long-term memory, persistent workspaces, and secrets for AI agents on infrastructure the enterprise controls. MinIO also announced a partnership with Datadog, which has certified AIStor as an The post MinIO AIStor Memory Reaches GA at SC26 as Datadog Certifies AIStor for On-Premises BYOC Logs appeared first on StorageReview.com.

## 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.

## Bring Datadog BYOC to your on-premises data with MinIO AIStor

DevFeed: [Bring Datadog BYOC to your on-premises data with MinIO AIStor](<https://devfeed.tech/articles/bring-datadog-byoc-to-your-on-premises-data-with-minio-aistor-142007.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/datadog-byoc-minio-aistor/>)

Author: Sarjeel Yusuf; Anusha Podila

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

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [datadog](<https://devfeed.tech/topics/datadog.md>), [MinIO](<https://devfeed.tech/topics/minio.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [bits ai](<https://devfeed.tech/topics/bits-ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [balance](<https://devfeed.tech/tags/balance.md>), [bits](<https://devfeed.tech/tags/bits.md>), [bits-ai](<https://devfeed.tech/tags/bits-ai.md>), [bring-your-own-cloud](<https://devfeed.tech/tags/bring-your-own-cloud.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [logs](<https://devfeed.tech/tags/logs.md>), [minio](<https://devfeed.tech/tags/minio.md>), [minio-aistor](<https://devfeed.tech/tags/minio-aistor.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>), [on-premises](<https://devfeed.tech/tags/on-premises.md>), [search](<https://devfeed.tech/tags/search.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

Datadog BYOC for Logs pairs Datadog's in-cluster indexing and search with MinIO AIStor object storage on infrastructure the organization controls. Observability Pipelines workers collect and process logs; indexers write searchable files to an AIStor bucket, while a PostgreSQL metastore tracks their locations and background compaction merges smaller files. Storage, indexing and search capacity can scale independently. Datadog searchers initiate TLS-encrypted outbound connections, authenticated with a Datadog API key, to query the on-premises data without inbound ports or a public endpoint. Log Explorer results pass through Datadog services for display but, according to the excerpt, are not stored or cached there; the indexed dataset stays in AIStor. The excerpt also describes RBAC, consent controls for Datadog support access, and disabling log samples or excluding log fields from notifications as privacy controls. AIStor erasure coding and object tiering support retention and storage-budget tradeoffs. BYOC currently supports logs; trace and metric support is described as coming soon.

### Source excerpt

Learn how Datadog BYOC and MinIO AIStor work together to help you search, monitor, and investigate logs while keeping your telemetry on-premises.

## 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...

## Datadog named a Leader in the 2026 Gartner® Magic Quadrant™ for Observability Pipelines

DevFeed: [Datadog named a Leader in the 2026 Gartner® Magic Quadrant™ for Observability Pipelines](<https://devfeed.tech/articles/datadog-named-a-leader-in-the-2026-gartner-magic-quadranttm-for-observability-pipelines-139519.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/datadog-observability-pipelines-gartner-magic-quadrant-2026/>)

Author: Yanbing Li

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

Content type: release

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

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

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [analyst](<https://devfeed.tech/tags/analyst.md>), [archive](<https://devfeed.tech/tags/archive.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cardinality](<https://devfeed.tech/tags/cardinality.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [collect](<https://devfeed.tech/tags/collect.md>), [collectors](<https://devfeed.tech/tags/collectors.md>), [connect](<https://devfeed.tech/tags/connect.md>), [context](<https://devfeed.tech/tags/context.md>), [control](<https://devfeed.tech/tags/control.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadranttm](<https://devfeed.tech/tags/gartner-magic-quadranttm.md>), [leader](<https://devfeed.tech/tags/leader.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observability-pipelines](<https://devfeed.tech/tags/observability-pipelines.md>)

### AI overview

Datadog says its Observability Pipelines product aggregates telemetry from agents, collectors, and open frameworks such as OpenTelemetry, standardizes it to teams' schemas (including OCSF for security data), and applies parsing, enrichment, and redaction before data leaves the network. It also offers filtering, sampling, lower-cost archiving, and routing one stream to Datadog, a SIEM, and archives, with destination changes that do not require reinstrumentation. Datadog presents these controls as ways to govern data and manage volume and cost across observability and security teams. The announcement says Gartner named Datadog a Leader in its 2026 Magic Quadrant; Gartner's disclaimer says its research reflects analyst opinions, is not an endorsement or vendor-selection recommendation, and should be considered within the full report.

### Source excerpt

Datadog has been recognized as a Leader in the 2026 Gartner® Magic Quadrant™ for Observability Pipelines.

## Naming is hard, semantics are hard(er): Inside Sentry Conventions

DevFeed: [Naming is hard, semantics are hard(er): Inside Sentry Conventions](<https://devfeed.tech/articles/naming-is-hard-semantics-are-hard-er-inside-sentry-conventions-136409.md>)

Original publisher: [Read original article](<https://blog.sentry.io/sentry-conventions/>)

Author: Lukas Stracke

Published: 2026-11-16T11:00:00Z

Content type: article

Language: en

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

Topics: [schema design](<https://devfeed.tech/topics/schema-design.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [programming-tips](<https://devfeed.tech/topics/programming-tips.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [align](<https://devfeed.tech/tags/align.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [has](<https://devfeed.tech/tags/has.md>), [inside](<https://devfeed.tech/tags/inside.md>), [meaning](<https://devfeed.tech/tags/meaning.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [product](<https://devfeed.tech/tags/product.md>), [sdks](<https://devfeed.tech/tags/sdks.md>), [semantics](<https://devfeed.tech/tags/semantics.md>), [sentry](<https://devfeed.tech/tags/sentry.md>)

### AI overview

Sentry Conventions provide a shared specification, based on and extending OpenTelemetry conventions, to align attribute names and meanings across SDKs, ingestion, querying, and product features. They define attribute types, scrubbing and deprecation rules, well-known values, span operations and naming, and metrics. JavaScript SDKs use the packages for attribute names and span operations; Relay applies scrubbing and infers missing span descriptions or names; Snuba and the backend coalesce deprecated and current attributes so queries work with either name. The product uses conventions for attribute descriptions, types, and deprecation-safe features. Sentry says it grew coverage from about 300 attributes to more than 900, while noting it is not complete. Its lessons include agreeing on specs before shipping, testing conventions, and treating migrations as worthwhile but painful.

### Source excerpt

How Sentry Conventions keep attribute names and their meaning aligned across our SDKs, our ingestion pipeline, and the Sentry product.

## Get useful logs from any source with Datadog Auto-Processing

DevFeed: [Get useful logs from any source with Datadog Auto-Processing](<https://devfeed.tech/articles/get-useful-logs-from-any-source-with-datadog-auto-processing-136095.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/auto-processing-log-pipelines/>)

Author: Nicolas Jung; Corey Brincks

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

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>)

Topics: [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [core](<https://devfeed.tech/tags/core.md>), [custom](<https://devfeed.tech/tags/custom.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data](<https://devfeed.tech/tags/data.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [formats](<https://devfeed.tech/tags/formats.md>), [keep](<https://devfeed.tech/tags/keep.md>), [log-management](<https://devfeed.tech/tags/log-management.md>), [logs](<https://devfeed.tech/tags/logs.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [processing](<https://devfeed.tech/tags/processing.md>), [rules](<https://devfeed.tech/tags/rules.md>), [source](<https://devfeed.tech/tags/source.md>), [structure](<https://devfeed.tech/tags/structure.md>), [structured](<https://devfeed.tech/tags/structured.md>), [updating](<https://devfeed.tech/tags/updating.md>)

### AI overview

Datadog Auto-Processing automatically detects custom logs without an applicable pipeline, generates parsing rules, and applies them when confidence and risk scores meet a required threshold; the process takes about an hour. It extracts queryable values and maps core fields such as timestamp, status, service, trace ID, and span ID, supporting consistent searches, dashboards, metrics, and monitors across different log formats. It also adapts pipelines it manages when formats drift, helping preserve attributes used by downstream workflows. Pipeline creation requires no manual initiation, rule writing, or approval. The excerpt does not specify how users can review or control generated rules.

### Source excerpt

Use Auto-Processing to structure logs with custom formats and keep them structured without manually building pipelines or updating parsing rules.

## Daemons can now send traces to Vercel Tracing

DevFeed: [Daemons can now send traces to Vercel Tracing](<https://devfeed.tech/articles/daemons-can-now-send-traces-to-vercel-tracing-133481.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-daemons-can-now-send-traces-to-vercel-tracing>)

Author: Gal Schlezinger

Published: 2026-11-13T22:24:00Z

Content type: release

Language: en

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

Topics: [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [automatic](<https://devfeed.tech/tags/automatic.md>), [cli](<https://devfeed.tech/tags/cli.md>), [export](<https://devfeed.tech/tags/export.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [search](<https://devfeed.tech/tags/search.md>), [service](<https://devfeed.tech/tags/service.md>), [socket](<https://devfeed.tech/tags/socket.md>), [spans](<https://devfeed.tech/tags/spans.md>), [traces](<https://devfeed.tech/tags/traces.md>), [unix](<https://devfeed.tech/tags/unix.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Daemons can export OpenTelemetry spans to Vercel Tracing through a per-daemon Unix socket whose path is provided in `VERCEL_OTEL_SOCKET_PATH`. For Node.js daemons, `@vercel/otel` 2.3.0 or later automatically detects the socket with default configuration; initialize OpenTelemetry before the worker starts. The Vercel CLI can search traces by project and service name and return JSON, including daemon spans from the last hour.

### Source excerpt

Vercel Daemons can now send OpenTelemetry traces to Vercel Tracing, allowing you and your agents to inspect background worker operations alongside the rest of your project's traces. Vercel provides each daemon with a Unix socket for receiving OTLP/HTTP traces and sets the socket's path in VERCEL_OTEL_SOCKET_PATH. Upgrading @vercel/otel to version 2.3.0 or later enables automatic trace export for Node.js daemons using the default configuration. The SDK detects this socket and sends the spans your worker records to Vercel. These spans are available through the Vercel CLI, which can search by service name within a project and return JSON for your agents. Learn more in the daemon tracing documentation. Read more

## Attackers are targeting the AI tools that produce our software

DevFeed: [Attackers are targeting the AI tools that produce our software](<https://devfeed.tech/articles/attackers-are-targeting-the-ai-tools-that-produce-our-software-133611.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/blog/generative-ai/attackers-are-targeting-the-ai-tools-that-produce-our-software>)

Author: Jim Gumbley, Gautam Koul

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

Content type: article

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [malware protection](<https://devfeed.tech/topics/malware-protection.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [breach](<https://devfeed.tech/tags/breach.md>), [build](<https://devfeed.tech/tags/build.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [coding-tools](<https://devfeed.tech/tags/coding-tools.md>), [commands](<https://devfeed.tech/tags/commands.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

AI coding tools and extensions sit close to source code, credentials, and build or deployment systems, so compromising one can expose broader environments. The article cites malicious Claude Code extension versions available through Cursor's marketplace for about 11 hours on October 29, 2026, and TeamPCP attacks on Trivy and LiteLLM as examples. It recommends six measures: assess dependencies using evidence and ongoing checks; make delivery teams responsible for adopted tools; control and verify updates; limit privileges and isolate tools with sandboxes and scoped credentials; prepare incident response, including workstation wipes and token revocation; and monitor developer machines while correlating endpoint, identity, repository, and cloud activity. The article presents these as risk-reduction steps, not a guarantee against compromise.

### Source excerpt

Attackers are targeting the AI tools that produce our software

## How to Build Centralized Observability in Dynatrace for YugabyteDB Audit and Query Logs

DevFeed: [How to Build Centralized Observability in Dynatrace for YugabyteDB Audit and Query Logs](<https://devfeed.tech/articles/how-to-build-centralized-observability-in-dynatrace-for-yugabytedb-audit-and-query-logs-126499.md>)

Original publisher: [Read original article](<https://www.yugabyte.com/blog/how-to-build-centralized-observability-in-dynatrace-for-yugabytedb-audit-and-query-logs/>)

Author: Nadeem Khan

Published: 2026-11-10T13:30:58Z

Content type: tutorial

Language: en

Sources: [The Distributed SQL Blog](<https://devfeed.tech/sources/the-distributed-sql-blog.md>)

Topics: [dynatrace](<https://devfeed.tech/topics/dynatrace.md>), [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [build](<https://devfeed.tech/tags/build.md>), [dynatrace](<https://devfeed.tech/tags/dynatrace.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>), [oltp](<https://devfeed.tech/tags/oltp.md>), [query](<https://devfeed.tech/tags/query.md>), [yugabytedb](<https://devfeed.tech/tags/yugabytedb.md>), [yugabytedb-anywhere](<https://devfeed.tech/tags/yugabytedb-anywhere.md>)

### AI overview

YugabyteDB Anywhere 2026.1 adds native OTLP export for logs and metrics, allowing query and audit logs to flow to Dynatrace or another OTLP-compatible receiver. Before v2026.1.2.0, enable `yb.telemetry.allow_otlp`; from v2026.1.2.0 it is enabled by default. Configure the receiver endpoint and authentication, then choose gRPC for a single endpoint when supported, or HTTP for HTTP-only receivers or separate log and metric URLs. The example enables DDL logging and logs queries exceeding 5000 ms, then routes query logs to Dynatrace. YBA provisions an OTEL collector on universe nodes; direct edits to its config can be reset by YBA operations. Dynatrace DQL can aggregate slow-query execution counts and latency statistics for dashboards and alerts. Audit logging is configurable through pgAudit and may add performance overhead, so enable only needed logging.

### Source excerpt

By integrating YugabyteDB Anywhere with Dynatrace via the native OTLP exporter, organizations can achieve a unified, proactive observability strategy seamlessly. This blog demonstrates how to build a unified Dynatrace dashboard that acts as a centralized command center for monitoring "slow queries" across all your clusters. Discover how organizations can harness these capabilities to continuously monitor slow queries across diverse environments, pinpointing latency bottlenecks and performance regressions before they affect end users. The post How to Build Centralized Observability in Dynatrace for YugabyteDB Audit and Query Logs appeared first on Yugabyte.

## When Missing Telemetry Is the Signal

DevFeed: [When Missing Telemetry Is the Signal](<https://devfeed.tech/articles/when-missing-telemetry-is-the-signal-127872.md>)

Original publisher: [Read original article](<https://opentelemetry.io/blog/2026/when-missing-telemetry-is-the-signal/>)

Author: OpenTelemetry Authors; Docs CC BY

Published: 2026-11-10T06:42:06Z

Content type: article

Language: en

Sources: [OpenTelemetry](<https://devfeed.tech/sources/blog-on-opentelemetry.md>)

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

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [collection](<https://devfeed.tech/tags/collection.md>), [collector](<https://devfeed.tech/tags/collector.md>), [compare](<https://devfeed.tech/tags/compare.md>), [completeness](<https://devfeed.tech/tags/completeness.md>), [context](<https://devfeed.tech/tags/context.md>), [count](<https://devfeed.tech/tags/count.md>), [counts](<https://devfeed.tech/tags/counts.md>), [data](<https://devfeed.tech/tags/data.md>), [data-loss](<https://devfeed.tech/tags/data-loss.md>), [error](<https://devfeed.tech/tags/error.md>), [events](<https://devfeed.tech/tags/events.md>), [processing](<https://devfeed.tech/tags/processing.md>), [reporting](<https://devfeed.tech/tags/reporting.md>), [service](<https://devfeed.tech/tags/service.md>), [signal](<https://devfeed.tech/tags/signal.md>), [stage](<https://devfeed.tech/tags/stage.md>), [storage](<https://devfeed.tech/tags/storage.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

An application can appear healthy while silently losing events, so telemetry completeness needs explicit checks beyond service availability and error rates. For an important workflow, define when signals should arrive, count accepted work and its outcomes at key boundaries, and reconcile accepted = completed + rejected + still processing while accounting for filtering, retries, batching, and normal delays. Use metrics with small, stable attributes to detect gaps; traces and correlated logs can help locate them, but sampling makes traces unsuitable as the sole completeness check. For asynchronous work, span links can preserve relationships without forcing a synchronous trace. A periodic synthetic event through the same stages checks end-to-end delivery, with a safe payload and a success window that allows queueing or batching. Also monitor OpenTelemetry Collector records accepted, refused, sent, or failed and exporter queue capacity; a running Collector may still fail to export. Interpret differences in light of configured filtering, sampling, routing, and processing, and observe the telemetry path independently where practical.

### Source excerpt

An empty dashboard can mean that nothing happened. It can also mean that the system stopped reporting what happened. On a dashboard, they look the same. One needs no action. The other means you are missing the information you need to act. Take a workflow where events enter a service, pass through a processing stage, and reach storage. An operator then uses the stored result. Every service can remain available while one data transfer silently drops events. Error rates stay low, yet the operator is working with an incomplete view.

## Make Kubernetes logs easier to correlate with traces using the log normalizer operator

DevFeed: [Make Kubernetes logs easier to correlate with traces using the log normalizer operator](<https://devfeed.tech/articles/make-kubernetes-logs-easier-to-correlate-with-traces-using-the-log-normalizer-operator-121178.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/06/make-kubernetes-logs-easier-to-correlate-with-traces-using-the-log-normalizer-operator>)

Author: Denis Moskalenko

Published: 2026-11-06T13:01:47Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [log management](<https://devfeed.tech/topics/log-management.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [kubectl](<https://devfeed.tech/topics/kubectl.md>)

Tags: [collector](<https://devfeed.tech/tags/collector.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [operator](<https://devfeed.tech/tags/operator.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

The Log Normalizer Operator standardizes heterogeneous Kubernetes logs at pod admission, enabling correlation with traces without changing application code. A namespace selector triggers a webhook to inject a sidecar and wrapper; the wrapper tees stdout and stderr through a named pipe, and the sidecar detects common formats, reassembles multiline entries, and emits structured JSON with fields such as timestamp, level, message, trace and span IDs, and Kubernetes identity. Records remain available through Kubernetes logs and can optionally go to an OpenTelemetry collector over OTLP; Korrel8r can use shared context, but its configuration and backends remain deployment-specific. The deployment model requires native sidecar support (Kubernetes 1.33+ or OpenShift 4.18+); existing pods need recreation, and failed image entrypoint resolution can leave a container unwrapped. The webhook's Ignore failure policy lets pods start without injection during outages. The sidecar complements rather than replaces the collector. Reported resource and latency measurements are workload-specific, and the operator does not define production redaction or sampling policies.

### Source excerpt

The log normalizer operator for Red Hat OpenShift injects a sidecar into selected pods, captures application output without requiring application code changes, detects the input format, reassembles multiline entries, and emits a consistent structured record. The normalized record remains available through kubectl logs and can also be exported to an OpenTelemetry collector over OTLP. The post Make Kubernetes logs easier to correlate with traces using the log normalizer operator appeared first on Red Hat Developer.

## What's new in network observability 1.12

DevFeed: [What's new in network observability 1.12](<https://devfeed.tech/articles/what-s-new-in-network-observability-1-12-119665.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/05/whats-new-network-observability-112>)

Author: Steven Lee

Published: 2026-11-05T14:51:22Z

Content type: release

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [eBPF](<https://devfeed.tech/topics/ebpf.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [netflow](<https://devfeed.tech/topics/netflow.md>), [container-networking](<https://devfeed.tech/topics/container-networking.md>)

Tags: [network](<https://devfeed.tech/tags/network.md>), [network-observability](<https://devfeed.tech/tags/network-observability.md>), [network-traffic](<https://devfeed.tech/tags/network-traffic.md>), [observability](<https://devfeed.tech/tags/observability.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-container-platform](<https://devfeed.tech/tags/openshift-container-platform.md>), [operator](<https://devfeed.tech/tags/operator.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [release](<https://devfeed.tech/tags/release.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Network Observability 1.12 adds configurable TLS tracking, which records connection details such as TLS version and cipher suite for visibility into cluster traffic. For eBPF agent to flowlogs-pipeline communication, TLS defaults to Auto using OpenShift annotations; operators can disable it or provide certificates for TLS or mTLS. Kafka compression supports gzip, Snappy, LZ4, and Zstandard for buffered and exported flows. A shared cache reduces API-server request spikes during FLP startup. Secondary network indexing now covers all secondary networks automatically; configured network names are deprecated and ignored, and an omitted index defaults to MAC and IP. Use `additionalIncludeList` to add predefined metrics without replacing the defaults. The release aligns with OpenShift Container Platform 4.22 and is backwards-compatible to 4.14.

### Source excerpt

Network observability is an optional operator for Red Hat OpenShift web console for insight into your network traffic and help with troubleshooting. With release 1.12, it aligns with Red Hat OpenShift Container Platform 4.22 and is backwards-compatible to 4.14. The post What's new in network observability 1.12 appeared first on Red Hat Developer.

## Hybrid LLM-Deterministic Pipelines for Enterprise-Scale Code Migration at Bloomberg

DevFeed: [Hybrid LLM-Deterministic Pipelines for Enterprise-Scale Code Migration at Bloomberg](<https://devfeed.tech/articles/hybrid-llm-deterministic-pipelines-for-enterprise-scale-code-migration-at-bloomberg-118051.md>)

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

Author: Mario Corchero, David Williams, Laszlo Kiss Kollar, Haowen Liu, Shivam Bairoliya, Gala Malbasic, Serkan Kirbas, Federica Sarro

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

Content type: article

Language: en

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

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [bloomberg](<https://devfeed.tech/tags/bloomberg.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [code](<https://devfeed.tech/tags/code.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [llm](<https://devfeed.tech/tags/llm.md>), [migration](<https://devfeed.tech/tags/migration.md>), [packaging](<https://devfeed.tech/tags/packaging.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [python](<https://devfeed.tech/tags/python.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### AI overview

Bloomberg's Automated Uplift initiative applied hybrid LLM and deterministic pipelines to two code migration campaigns: Python packaging across about 1,900 candidate repositories and a C++ build system migration across about 6,700. They generated 2,333 pull requests, with 729 successful migrations. The pipeline maximized deterministic processing, limiting the LLM to bounded file transformations using precomputed context, and incorporated production telemetry such as execution logs and usage traces. The abstract identifies review, testing, and deployment by repository owners as the main bottleneck, rather than migration generation. Pipeline verification before opening pull requests reduced these costs in the C++ campaign, where compilation and tests could be checked; fixes also carried over more readily across the more uniform repository population. The evidence here is the paper's abstract.

### Source excerpt

arXiv:2611.05457v1 Announce Type: new Abstract: Large organizations carry a long tail of infrastructure migrations that are worth doing but rarely urgent enough to compete with feature work, because each one costs significant engineering time per repository. This paper reports on our industrial experience from Automated Uplift, a multi-month initiative applying LLM-assisted migration pipelines across thousands of Bloomberg repositories. We examine two distinct production campaigns: a heterogeneous Python packaging migration (approx. 1,900 candidate repositories) and a uniform C++ build system migration (approx. 6,700 candidate repositories). Together, these campaigns generated 2,333 pull requests, resulting in 729 successful migrations. We detail our hybrid architectural solution which maximizes deterministic processing, confines the LLM to bounded file transformations within a pre-computed context, and incorporates runtime production telemetry (such as execution logs and usage traces). Our findings show that generating migrations turned out to be the easier part; the bottleneck was the cost, for owning teams, of reviewing, testing, and deploying them. These costs were lowered when changes could be verified directly in the pipeline before opening a PR (as with C++ compilation and test validation), and when the population was uniform enough for fixes to carry over from one repository to the next. We conclude by distilling our experience and findings into actionable, transferable patterns for architecting hybrid LLM-deterministic pipelines and scaling code migrations across the enterprise

## Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview

DevFeed: [Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview](<https://devfeed.tech/articles/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview-116280.md>)

Original publisher: [Read original article](<https://grafana.com/blog/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview/>)

Author: Bejal Lewis

Published: 2026-11-03T21:32:18Z

Content type: news

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collector](<https://devfeed.tech/tags/collector.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [engine](<https://devfeed.tech/tags/engine.md>), [engines](<https://devfeed.tech/tags/engines.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fleet-management](<https://devfeed.tech/tags/fleet-management.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [installation](<https://devfeed.tech/tags/installation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [loki](<https://devfeed.tech/tags/loki.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Alloy's OTel engine reached Public Preview in Alloy v1.21.0, offering native OpenTelemetry Collector pipelines alongside Alloy's cross-ecosystem default engine. It runs standard collector YAML without translation; existing `otelcol` workflows can use `alloy otel`, and deployments are supported through the upstream Helm chart, OpenTelemetry Operator v0.153.0+, or Alloy packages in OTel mode. Fleet Management can centrally apply configuration through the experimental `otel-supervisor` command. The engines cannot pass data directly; the experimental `alloyengine` extension runs Alloy configuration inside the collector as a bridge, but the article says it is unsupported for production. Examples include Database Observability and cloud provider exporters; native collector components are still in progress. Planned OTel work includes support bundles, while default-engine work targets more reliable Prometheus remote write and Loki delivery.

### Source excerpt

Many Grafana Cloud customers love what Alloy offers them, but we're also seeing a growing base of users who feel the same way about the OpenTelemetry Collector. We want to make it easy for customers to make the decision that makes the most sense, regardless of their preference. When we introduced the OpenTelemetry engine for Grafana Alloy, we set out to give teams a way to run native OTLP pipelines without giving up the power and flexibility Alloy is known for. Since then we've kept building: ironing out service installation support, enabling Fleet Management, and folding in feedback from early users. Today, as of Alloy v1.21.0, we're happy to share that the OTel engine has moved into Public Preview, running right alongside the default engine you already know. In this post, we'll dig into when you'd reach for each engine, walk through some of the most interesting use cases we've seen so far, and give a preview of where both engines are headed next. The motivation behind each engine Before diving into specific new features, let's recap why we have two engines in Alloy. Default engine The default engine is a cross-ecosystem engine at its core; it's not tied to any single wire format or vendor. It can just as easily run a Prometheus pipeline, an OTLP pipeline, or a Loki pipeline, all defined using Alloy's own configuration syntax. That flexibility is what makes it a Swiss army knife: the same engine that scrapes Prometheus metrics can pull in logs over syslog for logs, ingest OTLP, scrape Prometheus metrics from embedded exporters, and route all of it to wherever it needs to go. OpenTelemetry engine There's a lot to like about being able to speak every ecosystem's language. But the telemetry landscape itself is moving in the opposite direction. Rather than translating between formats, the industry is increasingly converging on a single, shared model defined by the OpenTelemetry specification. That's what an OpenTelemetry Collector actually is: a pipeline that treats OT

## The 2026 Observability Forecast: India Edition

DevFeed: [The 2026 Observability Forecast: India Edition](<https://devfeed.tech/articles/the-2026-observability-forecast-india-edition-114953.md>)

Original publisher: [Read original article](<https://newrelic.com/blog/observability/the-observability-forecast-2026-india>)

Author: Lisa Banks

Published: 2026-11-02T12:00:00Z

Content type: article

Language: en

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

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-application](<https://devfeed.tech/tags/ai-application.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [forecast](<https://devfeed.tech/tags/forecast.md>), [india](<https://devfeed.tech/tags/india.md>), [new-relic](<https://devfeed.tech/tags/new-relic.md>), [observability](<https://devfeed.tech/tags/observability.md>), [research](<https://devfeed.tech/tags/research.md>), [study](<https://devfeed.tech/tags/study.md>), [survey](<https://devfeed.tech/tags/survey.md>)

### AI overview

In the survey's India sample of 500 IT and engineering respondents, rapid AI adoption and OpenTelemetry standardisation coincide with severe operational strain. 56% report monitoring AI agents in production, versus 35% globally, and 42% are fully standardised on OpenTelemetry, versus 22% globally. Yet Indian enterprises average six observability tools, and only 20% say AI-assisted observability significantly improved event correlation. High-impact outages occur multiple times per day at 31% of organisations; the reported average hourly revenue cost is $2.43 million, with an estimated $3 million per average high-impact outage. The excerpt says organisations pairing AI adoption and OpenTelemetry with unified platform visibility are more likely to report 3x-5x financial returns, while fragmented environments are associated with firefighting and high outage costs. These are survey findings, not evidence of causation.

### Source excerpt

New Relic partnered with Enterprise Technology Research (ETR) to survey 2,575 IT and engineering leaders and practitioners worldwide. 500 of these are based in India, 20% of the global sample and the second largest single-country cut in the study.

## Connecting Cloudflare and Honeybadger with OpenTelemetry

DevFeed: [Connecting Cloudflare and Honeybadger with OpenTelemetry](<https://devfeed.tech/articles/connecting-cloudflare-and-honeybadger-with-opentelemetry-109204.md>)

Original publisher: [Read original article](<https://www.honeybadger.io/blog/cloudflare-honeybadger-otel/>)

Author: Addison Curtis

Published: 2026-10-29T07:00:00Z

Content type: tutorial

Language: en

Sources: [Honeybadger](<https://devfeed.tech/sources/honeybadger.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [devops-articles](<https://devfeed.tech/tags/devops-articles.md>), [honeybadger](<https://devfeed.tech/tags/honeybadger.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>)

### AI overview

The article explains how to send Cloudflare Workers logs to Honeybadger Insights over OpenTelemetry Protocol (OTLP). In Cloudflare, create a Logs destination with endpoint `https://api.honeybadger.io/v1/logs` and add the project API key as a custom `X-API-Key` header; the header name must match exactly. The author tests the pipeline by logging from a Worker route, checking Cloudflare for the event, then allowing a few minutes for it to reach Insights. The article says Cloudflare's built-in observability may suffice for small apps, while its split between logs and traces and fragmented query builder can make analysis harder for larger applications. Insights instead presents wide events and offers querying, visualizations, natural-language search, and alarms. The example uses RedwoodSDK and requires a `workers.dev` subdomain; it focuses on logs, although the article notes that Cloudflare supports OTel traces and logs and Insights supports OTLP traces, metrics, and logs.

### Source excerpt

Cloudflare's built-in observability works fine for small apps, but the search is clunky and your data gets split across events and traces. Here's how to pipe Cloudflare Workers logs into Honeybadger Insights with OpenTelemetry instead.

## Elastic Cloud Serverless audit logs: Ship the trail to Observability or Security

DevFeed: [Elastic Cloud Serverless audit logs: Ship the trail to Observability or Security](<https://devfeed.tech/articles/elastic-cloud-serverless-audit-logs-ship-the-trail-to-observability-or-security-106464.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/elastic-cloud-serverless-audit-logs>)

Author: Valentin Crettaz

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [Security](<https://devfeed.tech/topics/security.md>), [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [detection](<https://devfeed.tech/tags/detection.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elastic-cloud-serverless](<https://devfeed.tech/tags/elastic-cloud-serverless.md>), [forensics](<https://devfeed.tech/tags/forensics.md>), [kibana](<https://devfeed.tech/tags/kibana.md>), [logs](<https://devfeed.tech/tags/logs.md>), [object](<https://devfeed.tech/tags/object.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operations](<https://devfeed.tech/tags/operations.md>), [rules](<https://devfeed.tech/tags/rules.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [space](<https://devfeed.tech/tags/space.md>)

### AI overview

Elastic Cloud Serverless log delivery is generally available for shipping a source project's Elasticsearch and Kibana activity to an Observability or Security project in the same organization. Multiple sources can share a destination; ingest and retention are billed there, and retention is configurable. Five Ignore filters can drop matching events before delivery to reduce volume and cost. The stream covers saved-object changes, index access, sign-ins and access failures, with project and producer fields for attribution. Eight included alert rules watch for credential attack patterns; the first-seen identity rule needs at least a day of history. Seven dashboards include Kibana Object Forensics, Elasticsearch Data Access and Identity & Access. Enabling delivery requires Admin or Editor access on the source project. Organization administration logs are described as upcoming, not part of this release.

### Source excerpt

Eight alerting rules and seven dashboards arrive with the logs, including Kibana Object Forensics, where a deleted detection rule shows up with the person who deleted it and the space it was in.

## Observing AWS Lambda durable functions with the Durable Execution Telemetry Exporter

DevFeed: [Observing AWS Lambda durable functions with the Durable Execution Telemetry Exporter](<https://devfeed.tech/articles/observing-aws-lambda-durable-functions-with-the-durable-execution-telemetry-exporter-106353.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/observing-aws-lambda-durable-functions-with-the-durable-execution-telemetry-exporter/>)

Author: Pooya Paridel

Published: 2026-10-28T19:36:12Z

Content type: tutorial

Language: en

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

Topics: [serverless monitoring](<https://devfeed.tech/topics/serverless-monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [athena](<https://devfeed.tech/tags/athena.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [durable-execution](<https://devfeed.tech/tags/durable-execution.md>), [durable-functions](<https://devfeed.tech/tags/durable-functions.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [query](<https://devfeed.tech/tags/query.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

The Durable Execution Telemetry Exporter reconstructs a cumulative JSON record for each AWS Lambda durable execution from checkpointed SDK state, so teams can query steps, timing, retries, status, and errors without correlating invocation logs. A one-line SDK integration can write to CloudWatch Logs by default or route records to configured destinations; emit mode, deterministic sampling, and content transforms control frequency and exposed data. Size limits can truncate records per destination while preserving identity and timeline fields. The companion local MCP server offers read-only tools to inspect schemas, list or fetch executions, and query supported destinations; SQL queries must be SELECT or WITH ending in SELECT. Limits include no records for service-originated STOPPED or TIMED_OUT states without an invocation, dropped intermediate snapshots when exports lag, and extra replay cost when preserving child operations across resumes.

### Source excerpt

Durable functions span many Lambda invocations, so per-invocation logs answer the wrong question. The Durable Execution Telemetry Exporter is an SDK plugin that emits one complete record per execution to any of 13 destinations with a one-line change, and a companion MCP server lets an AI agent query that data in plain language.

## OpenTelemetry Transformation Language reaches v1

DevFeed: [OpenTelemetry Transformation Language reaches v1](<https://devfeed.tech/articles/opentelemetry-transformation-language-reaches-v1-103664.md>)

Original publisher: [Read original article](<https://opentelemetry.io/blog/2026/ottl-v1/>)

Author: OpenTelemetry Authors; Docs CC BY

Published: 2026-10-27T15:00:47Z

Content type: release

Language: en

Sources: [OpenTelemetry](<https://devfeed.tech/sources/blog-on-opentelemetry.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [data transformation](<https://devfeed.tech/topics/data-transformation.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [contrib](<https://devfeed.tech/tags/contrib.md>), [functions](<https://devfeed.tech/tags/functions.md>), [language](<https://devfeed.tech/tags/language.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [stable](<https://devfeed.tech/tags/stable.md>), [syntax](<https://devfeed.tech/tags/syntax.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>), [transformation](<https://devfeed.tech/tags/transformation.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Starting with opentelemetry-collector-contrib v0.164.0, OTTL is stable for traces, metrics, and logs, with 1.x compatibility for documented syntax, standard functions, and the Go API used by custom components. Existing statements are promised to parse and behave the same in later 1.x releases. Because standard functions become permanent, new ones begin as experimental in the 0.x `xottl` module and require the `pkg.ottl.functions.enableExperimental` feature gate; promotion requires at least two minor releases, tests and documentation, no open change proposals, and user demand. Lambda functions remain experimental behind a separate gate, and profiles support remains in separately versioned `xprofile`. Before upgrading, remove obsolete feature gates, including `ottl.set.allowNil` for v0.164.0, and consult intervening `pkg/ottl` changelog entries when skipping releases. The transform processor is being prepared for stability but is not yet described as stable.

### Source excerpt

The OpenTelemetry Transformation Language (OTTL) is now v1. Starting with opentelemetry-collector-contrib v0.164.0, OTTL is stable for traces, metrics, and logs. The release of v1 means OTTL meets the Collector's 'stable' stability criteria for testing, benchmarking, documentation, and telemetry. It also comes with a compatibility promise for all of 1.x. If you write OTTL statements, the syntax and the standard functions stay backward compatible. If you build your own components on top of OTTL, the Go API will also remain compatible.

## Filtering and reducing AI agent telemetry with the OpenTelemetry Collector

DevFeed: [Filtering and reducing AI agent telemetry with the OpenTelemetry Collector](<https://devfeed.tech/articles/filtering-and-reducing-ai-agent-telemetry-with-the-opentelemetry-collector-95359.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/10/22/filtering-and-reducing-ai-agent-telemetry-with-the-opentelemetry-collector/>)

Author: Adnan Rahic, Bindplane by Dynatrace

Published: 2026-10-22T11:00:00Z

Content type: tutorial

Language: en

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

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Logging and metrics](<https://devfeed.tech/topics/logging-and-metrics.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [all](<https://devfeed.tech/tags/all.md>), [blog](<https://devfeed.tech/tags/blog.md>), [can](<https://devfeed.tech/tags/can.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [collector](<https://devfeed.tech/tags/collector.md>), [it-s](<https://devfeed.tech/tags/it-s.md>), [make](<https://devfeed.tech/tags/make.md>), [native](<https://devfeed.tech/tags/native.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [store](<https://devfeed.tech/tags/store.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [text](<https://devfeed.tech/tags/text.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

An OpenTelemetry Collector can reduce Claude Code telemetry volume while retaining the six operational answers the author needs. In a sample run, the author reports 181 records and 289 KB of JSON, with prompts, tool content and per-session metric labels driving much of the cost. The proposed setup fans one OTLP receiver into raw and optimized pipelines for comparison. It drops selected log events and fields, hashes user and session IDs, removes metric dimensions and merges session datapoints before delta-to-cumulative conversion, and filters successful tool-execution spans while trimming large span-event content. The author reports metric cardinality falling from 300 series to 12, optimized totals matching raw within 0.5%, and log and trace bytes roughly halving without trace sampling. Metric merging requires one Collector to see every session, so the author places it on a single gateway behind a load balancer. Tail sampling is offered as a further reduction option, with the caveat that its decision delay can miss failures that occur later in long interactions.

### Source excerpt

Turn on an AI coding agent's telemetry and it throws a wall of text at you. It's expensive to store and what's worse, you can't make sense of it. It's all OpenTelemetry native, though. So you...

## AI Root Cause Analysis: LLM-Powered Root-Cause Analysis for Distributed Systems

DevFeed: [AI Root Cause Analysis: LLM-Powered Root-Cause Analysis for Distributed Systems](<https://devfeed.tech/articles/ai-root-cause-analysis-llm-powered-root-cause-analysis-for-distributed-systems-109739.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/ai-root-cause-analysis/>)

Author: Ales Justin

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bridges](<https://devfeed.tech/tags/bridges.md>), [but](<https://devfeed.tech/tags/but.md>), [cause](<https://devfeed.tech/tags/cause.md>), [complete](<https://devfeed.tech/tags/complete.md>), [context](<https://devfeed.tech/tags/context.md>), [details](<https://devfeed.tech/tags/details.md>), [developers](<https://devfeed.tech/tags/developers.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [llm](<https://devfeed.tech/tags/llm.md>), [root](<https://devfeed.tech/tags/root.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

AI Root Cause Analysis is an open-source Quarkus application that uses MCP to gather traces from Tempo, correlated logs from Loki, and time-matched metrics from Prometheus, then asks an LLM to produce structured findings on root causes, severity, cascading failures, and remediation. A StripMcpClient filters telemetry noise before it reaches the model; the source reports reducing one metrics set from 586 entries to about 35. Optional Quarkus Dev MCP integration lets it examine application code and write generated Grafana dashboards into app workspaces. Without that integration, core telemetry analysis still works, but source examination is disabled and dashboards must be copied from the UI and imported manually. The excerpt lists OpenAI (default), Grok, Gemini, and WatsonX profiles; Anthropic and native-image support are described as future priorities.

### Source excerpt

When something goes wrong in a distributed system, engineers face the same ritual: open Grafana, dig through traces in Tempo, correlate logs in Loki, check Prometheus metrics, and mentally piece together a causal chain across services. What if an LLM could do that for you -- pulling telemetry from the same tools you already use and producing a structured root-cause analysis in seconds? That's what AI Root Cause Analysis does. It's an open-source Quarkus application that connects to your existing Grafana LGTM stack via MCP (Model Context Protocol), feeds correlated traces, logs, and metrics to an LLM, and returns actionable analysis -- complete with root causes, severity assessments, and remediation suggestions. Who Is This For? AI Root Cause Analysis is built for developers who work with distributed systems but don't want to become observability experts. You know your LGTM stack is collecting traces, logs, and metrics -- but correlating them across services, spotting the root cause in a wall of spans, and distinguishing symptoms from causes takes experience and time. The AI handles that for you: it knows how to query Tempo, Loki, and Prometheus, understands what the telemetry means in context, and draws correlations that would take manual investigation to piece together. If you're comfortable with AI but not with the details of trace propagation, span hierarchies, or PromQL -- this tool bridges that gap. What It Does AI Root Cause Analysis is a standalone analysis engine. Point it at your LGTM stack and your running applications, and it will: Retrieve recent traces from Tempo via MCP and identify the interesting ones (errors, high latency, unusual patterns) Correlate logs for each trace from Loki, linking log entries to specific spans Pull Prometheus metrics at the time window of each trace to add system-level context Analyze everything together using an LLM, producing a structured report that distinguishes root causes from symptoms, identifies cascading failures, and s

## How Proscia built unlimited observability with Amazon S3 and the Altinity Kubernetes Operator

DevFeed: [How Proscia built unlimited observability with Amazon S3 and the Altinity Kubernetes Operator](<https://devfeed.tech/articles/how-proscia-built-unlimited-observability-with-amazon-s3-and-the-altinity-kubernetes-operator-93049.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/how-proscia-built-unlimited-observability-with-amazon-s3-and-the-altinity-kubernetes-operator/>)

Author: Kyriakos Toulgaridis

Published: 2026-10-21T16:40:04Z

Content type: article

Language: en

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

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-block-storage-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-storage-amazon-ebs.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws-cloud-storage](<https://devfeed.tech/tags/aws-cloud-storage.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-key-management-service-aws-kms](<https://devfeed.tech/tags/aws-key-management-service-aws-kms.md>), [can](<https://devfeed.tech/tags/can.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [company](<https://devfeed.tech/tags/company.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data](<https://devfeed.tech/tags/data.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [eks](<https://devfeed.tech/tags/eks.md>), [gdpr](<https://devfeed.tech/tags/gdpr.md>), [hipaa](<https://devfeed.tech/tags/hipaa.md>), [it](<https://devfeed.tech/tags/it.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operator](<https://devfeed.tech/tags/kubernetes-operator.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operator](<https://devfeed.tech/tags/operator.md>), [s3](<https://devfeed.tech/tags/s3.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Proscia built a self-managed observability platform across AWS accounts and Regions: OpenTelemetry collectors send telemetry to a dedicated account, where ClickHouse runs on EKS under the Altinity Kubernetes Operator. Recent data stays on EBS SSDs; TTL rules move colder data to S3, and backups also go to S3. The design combines high-cardinality queries, long retention, and healthcare compliance controls, with Grafana for dashboards and alerting and an MCP interface for natural-language queries. Proscia reports handling 33 billion records monthly, over 10 times more data at roughly the same overall cost as its prior SaaS service, 100 times lower storage cost per TB, and median root cause analysis in 10 minutes versus a prior 4-24-hour escalation round trip. Building requires engineering capacity to operate stateful Kubernetes systems; the text suggests a hybrid approach using managed ClickHouse or hosted visualization when that is a poor fit.

### Source excerpt

Observability can claim a growing share of IT budgets. Learn how Proscia, a pathology AI company, built a self-hosted observability platform on Amazon S3, Amazon EKS, and ClickHouse managed by the Altinity Kubernetes Operator, achieving unlimited telemetry retention at object-storage cost under HIPAA, GDPR, and data-residency requirements.

## Distributed tracing for CI pipelines without touching a single workflow file

DevFeed: [Distributed tracing for CI pipelines without touching a single workflow file](<https://devfeed.tech/articles/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file-109908.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/10/21/distributed-tracing-for-ci-pipelines-without-touching-a-single-workflow-file-2/>)

Author: George Sims, Proton.me

Published: 2026-10-21T11:00:00Z

Content type: tutorial

Language: en

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

Topics: [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [ci](<https://devfeed.tech/tags/ci.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

A single org-level GitHub webhook can send workflow_run and workflow_job events to an OpenTelemetry Collector's alpha githubreceiver, which turns them into hierarchical OTLP traces without editing workflow files. The article recommends pinning the collector version, supplying a dummy scraper entry because configuration validation requires it, and securing the publicly reachable endpoint with GitHub IP restrictions or a WAF; org admin access is needed, and GitHub Enterprise Server delivery should be validated. To estimate cost, count repos with real activity in a typical week, then estimate runs, steps, spans, and data volume and compare it with existing tracing traffic. The resulting traces cover workflows, jobs, and steps, including new repos. For self-hosted Actions Runner Controller fleets, this complements ARC's runner-fleet metrics by showing workflow-level delays and flakiness. Alerting design is outside the article's scope.

### Source excerpt

You've probably felt this one: GitHub Actions usage creeps up across your org, and your actual visibility into it doesn't keep pace. Which workflows are slow? Which are flaky? How long are jobs sitting queued for...

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