# Prometheus

Prometheus is an open-source monitoring system and time series database for collecting, storing, querying, and alerting on metrics from applications, systems, and services.

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

## 4 GB of Logs a Minute: A Kafka Monitoring Incident With 20 Minutes to Spare

DevFeed: [4 GB of Logs a Minute: A Kafka Monitoring Incident With 20 Minutes to Spare](<https://devfeed.tech/articles/4-gb-of-logs-a-minute-a-kafka-monitoring-incident-with-20-minutes-to-spare-146459.md>)

Original publisher: [Read original article](<https://linuxhandbook.com/blog/kafka-monitoring-incident/>)

Author: Yash Kiran Patil

Published: 2026-11-20T09:34:13Z

Content type: tutorial

Language: en

Sources: [Linux Handbook](<https://devfeed.tech/sources/linux-handbook.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [incident management](<https://devfeed.tech/topics/incident-management.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Logging and metrics](<https://devfeed.tech/topics/logging-and-metrics.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [availability](<https://devfeed.tech/tags/availability.md>), [blog](<https://devfeed.tech/tags/blog.md>), [bounded](<https://devfeed.tech/tags/bounded.md>), [broker](<https://devfeed.tech/tags/broker.md>), [bug](<https://devfeed.tech/tags/bug.md>), [canary](<https://devfeed.tech/tags/canary.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cause](<https://devfeed.tech/tags/cause.md>), [change](<https://devfeed.tech/tags/change.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [contain](<https://devfeed.tech/tags/contain.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [incident](<https://devfeed.tech/tags/incident.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [logs](<https://devfeed.tech/tags/logs.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [time](<https://devfeed.tech/tags/time.md>), [warnings](<https://devfeed.tech/tags/warnings.md>)

### AI overview

A partial JMX Exporter upgrade left Kafka brokers on versions 1.6.0 and 0.9.0; under the new scrape configuration, older agents emitted rapidly growing Jetty warnings, putting disk capacity at risk before traffic began. The account links the warnings to the mixed rollout but says their precise cause is unproven without request paths, responses, configuration, and stack traces. Operators used a supervised loop to truncate one verified active log and buy time, preserving a warning sample first; this destructive workaround does not fix exporter behavior or reclaim space from deleted-but-open files. The durable response was to standardize agent versions and restart brokers one at a time during a maintenance window, checking cluster health and exporter and Prometheus metrics after each restart. The article recommends bounded log retention, version inventory, canary checks, and measured tuning rather than assuming an endpoint or concurrency bug.

### Source excerpt

A mixed JMX Exporter fleet, rapidly growing Jetty warnings, and the difference between buying time and fixing the cause.

## Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache

DevFeed: [Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache](<https://devfeed.tech/articles/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache-144311.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache/>)

Author: Paul Ross

Published: 2026-11-19T18:39:15Z

Content type: tutorial

Language: en

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

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-managed-grafana](<https://devfeed.tech/tags/amazon-managed-grafana.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [latency](<https://devfeed.tech/tags/latency.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node](<https://devfeed.tech/tags/node.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [query](<https://devfeed.tech/tags/query.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache for Valkey sends engine and host metrics to CloudWatch in OpenTelemetry format without an exporter or collector. The article demonstrates using ElastiCache Insights to locate a hot shard or node, then PromQL to rank nodes, inspect command latency, and alarm across all nodes as cluster membership changes. Standard monitoring publishes core metrics every 60 seconds; selected detailed metrics arrive every 15 seconds and can expose short latency spikes that a longer window smooths out. Core metrics and ElastiCache Insights are free, while selected detailed metrics, PromQL API scans, and alarms incur charges. The walkthrough requires a node-based Valkey cluster in a supported Region; its Grafana guidance covers version 13 or later, with a separate Prometheus data source approach for version 12.4.

### Source excerpt

Amazon ElastiCache for Valkey now offers OpenTelemetry metrics, detailed monitoring, ElastiCache Insights, and PromQL. This post walks through one troubleshooting path: turn on detailed monitoring, find a hot shard, query with PromQL, catch a short latency spike, and create one alarm that watches every node.

## Debezium 3.8.0.Alpha2 Released

DevFeed: [Debezium 3.8.0.Alpha2 Released](<https://devfeed.tech/articles/debezium-3-8-0-alpha2-released-143957.md>)

Original publisher: [Read original article](<https://debezium.io/blog/2026/11/19/debezium-3-8-alpha2-released/>)

Author: Chris Cranford

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

Content type: release

Language: en

Sources: [Debezium](<https://devfeed.tech/sources/debezium-io.md>)

Topics: [Debezium Connector](<https://devfeed.tech/topics/debezium-connector.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [announce](<https://devfeed.tech/tags/announce.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [capture](<https://devfeed.tech/tags/capture.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [debezium](<https://devfeed.tech/tags/debezium.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [details](<https://devfeed.tech/tags/details.md>), [faster](<https://devfeed.tech/tags/faster.md>), [formats](<https://devfeed.tech/tags/formats.md>), [full](<https://devfeed.tech/tags/full.md>), [message](<https://devfeed.tech/tags/message.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [more](<https://devfeed.tech/tags/more.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [platform](<https://devfeed.tech/tags/platform.md>)

### AI overview

Debezium 3.8.0.Alpha2 adds initial and initial-only snapshots to the TiDB connector, which capture a consistent view without locking tables before streaming continues. The Oracle connector changes snapshot locking: shared mode holds table locks while data is read, so most DDL waits; extended mode blocks all DDL and pauses writes, subject to `snapshot.lock.timeout.ms`. Remove the no-longer-recognized `snapshot.database.errors.max.retries` setting. For databases using extended strings, a recovery snapshot rebuilds schema history with byte-size data. Other notable changes include configurable pipeline message formats and secured Prometheus monitoring in Debezium Platform; Oracle LogMiner query performance nearly tripled in a 1,000-table benchmark; and MongoDB change-stream buffers gain event and byte limits. This is an alpha preview with Oracle upgrade considerations and many connector fixes.

### Source excerpt

With November in full swing, we're pleased to announce Debezium 3.8.0.Alpha2, the second preview release of the 3.8 series. This release brings initial snapshots to the TiDB connector. Debezium Platform gains configurable message formats for pipelines and monitoring that works with secured Prometheus deployments. Oracle LogMiner users get faster and more reliable change capture, and there are many bug fixes across the connectors. There are a few breaking changes for the Oracle connector to review before upgrading. Read on for the full details!

## Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.

DevFeed: [Your Kubernetes Knowledge Is Becoming Cheaper. Your Production Judgment Isn't.](<https://devfeed.tech/articles/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isn-t-136242.md>)

Original publisher: [Read original article](<https://blog.devops.dev/your-kubernetes-knowledge-is-becoming-cheaper-your-production-judgment-isnt-cabf2adfc61a?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-11-16T13:25:19Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bash](<https://devfeed.tech/tags/bash.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-pipeline](<https://devfeed.tech/tags/ci-cd-pipeline.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [commands](<https://devfeed.tech/tags/commands.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [decision](<https://devfeed.tech/tags/decision.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-engineer](<https://devfeed.tech/tags/devops-engineer.md>), [docker](<https://devfeed.tech/tags/docker.md>), [english](<https://devfeed.tech/tags/english.md>), [git](<https://devfeed.tech/tags/git.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [helm](<https://devfeed.tech/tags/helm.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

The article argues that AI is making configuration such as Kubernetes YAML, Terraform modules, and CI/CD pipelines cheaper to produce, while production judgment remains central to DevOps. It recommends narrowing investigations with evidence, checking the failure's scope and system layer, and treating dashboards as signals rather than proof of user health. Before restarting, rolling back, draining, scaling, or failing over, assess consequences and blast radius; under uncertainty, seek a safe next test. During incidents, communicate impact, hypothesis, evidence being checked, and next action. It also urges engineers to learn failure modes alongside tool mechanics. These are the article's recommendations, not a comparison of specific AI tools.

### Source excerpt

There was a time when knowing how to write Kubernetes YAML felt like a superpower. You knew Deployments. You knew Services. You knew ConfigMaps. You knew Ingress. You knew how to write a Helm chart without accidentally deleting half the cluster. You learned Terraform. You learned Jenkins. You learned Bash. You learned Prometheus queries. You spent years collecting tools, commands, syntax, and implementation patterns. And then AI showed up. Now you can describe what you want in plain English and get a Terraform module. Ask for a Kubernetes Deployment and you get YAML. Ask for a CI/CD pipeline and you get a pipeline. Ask for a Bash script and you get one. Ask for a PromQL query and, assuming the machines haven't collectively decided to punish humanity that day, you get something reasonably useful. 😄 So here's the uncomfortable question: If AI can increasingly handle implementation, what exactly becomes more valuable for a DevOps engineer? I think the answer is simple. Judgment. Not knowing more commands. Not memorizing more YAML. Not collecting another 47 certifications. Knowing what to do when the obvious answer doesn't work. And production has a beautiful way of ensuring that the obvious answer almost never works. 1 The Shift: From Tool Operator to Decision Maker For years, DevOps careers were heavily associated with tools. Learn AWS. Learn Docker. Learn Kubernetes. Learn Terraform. Learn Jenkins. Learn Ansible. Learn Prometheus. Learn Grafana. Learn Git. Learn Linux. And yes, these skills still matter. The tools aren't suddenly useless because AI can generate configuration for them. But something important is changing. The cost of producing configuration is falling. Consider a simple Kubernetes deployment. Previously, an engineer might spend time writing: apiVersion: apps/v1 kind: Deployment metadata: name: payment-api spec: replicas: 3 selector: matchLabels: app: payment-api template: metadata: labels: app: payment-api spec: containers: - name: payment-api image

## Scalability Testing: Techniques, Metrics, and Tools

DevFeed: [Scalability Testing: Techniques, Metrics, and Tools](<https://devfeed.tech/articles/scalability-testing-techniques-metrics-and-tools-133443.md>)

Original publisher: [Read original article](<https://testgrid.io/blog/scalability-testing/>)

Author: Yogesh Solanki

Published: 2026-11-13T13:14:58Z

Content type: article

Language: en

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

Topics: [Performance Testing](<https://devfeed.tech/topics/performance-testing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [k6](<https://devfeed.tech/topics/k6.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [database](<https://devfeed.tech/tags/database.md>), [handle](<https://devfeed.tech/tags/handle.md>), [know](<https://devfeed.tech/tags/know.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [more](<https://devfeed.tech/tags/more.md>), [performance](<https://devfeed.tech/tags/performance.md>), [quality-assurance-qa](<https://devfeed.tech/tags/quality-assurance-qa.md>), [quickly](<https://devfeed.tech/tags/quickly.md>), [resources](<https://devfeed.tech/tags/resources.md>), [rise](<https://devfeed.tech/tags/rise.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [scalability-testing](<https://devfeed.tech/tags/scalability-testing.md>), [techniques](<https://devfeed.tech/tags/techniques.md>), [testing](<https://devfeed.tech/tags/testing.md>), [testing-techniques](<https://devfeed.tech/tags/testing-techniques.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Scalability testing measures how performance changes as workload or capacity grows, including whether response times, throughput, stability, and resource use remain within defined goals. The excerpt outlines load, stress, spike, soak, volume, and capacity tests, plus testing vertical and horizontal scaling. Its workflow sets performance criteria, prepares a representative environment and realistic workloads, automates scripts, integrates checks into CI/CD, and monitors results to locate bottlenecks and guide changes to code, databases, caching, infrastructure, or scaling policies. Named tools differ by role: K6, Gatling, JMeter, LoadRunner, and Locust simulate workloads; Grafana, Prometheus, Datadog, New Relic, Dynatrace, and CloudWatch monitor system signals. The excerpt also describes TestGrid workflows using JMeter and mobile device performance signals. It does not provide the promised detailed metrics list or infrastructure table.

### Source excerpt

You know your application can handle 5,000 users. What happens at 10,000? More importantly, what happens between the two? Does throughput rise with the additional capacity? Do response times remain within your SLO? Does the database become the bottleneck? Does autoscaling respond quickly enough, or does performance deteriorate before new resources arrive? Scalability testing answers [...]

## Allocate shared Amazon MSK costs to Kafka topics for cost visibility

DevFeed: [Allocate shared Amazon MSK costs to Kafka topics for cost visibility](<https://devfeed.tech/articles/allocate-shared-amazon-msk-costs-to-kafka-topics-for-cost-visibility-129557.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/allocate-shared-amazon-msk-costs-to-kafka-topics-for-cost-visibility/>)

Author: Durai Krishnan

Published: 2026-11-11T19:46:04Z

Content type: article

Language: en

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

Topics: [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon Managed Service for Prometheus](<https://devfeed.tech/topics/amazon-managed-service-for-prometheus.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Parquet files in Amazon S3](<https://devfeed.tech/topics/parquet-files-in-amazon-s3.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [aws-sns](<https://devfeed.tech/topics/aws-sns.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-managed-service-for-prometheus](<https://devfeed.tech/tags/amazon-managed-service-for-prometheus.md>), [amazon-managed-streaming-for-apache-kafka-amazon-msk](<https://devfeed.tech/tags/amazon-managed-streaming-for-apache-kafka-amazon-msk.md>), [amazon-msk](<https://devfeed.tech/tags/amazon-msk.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>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cost-and-usage-report](<https://devfeed.tech/tags/aws-cost-and-usage-report.md>), [billing](<https://devfeed.tech/tags/billing.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-and-usage-report](<https://devfeed.tech/tags/cost-and-usage-report.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [topic](<https://devfeed.tech/tags/topic.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

The pipeline estimates each Kafka topic's share of an Amazon MSK Provisioned cluster's daily cost by joining cluster-level CUR charges with per-topic ingress metrics, mapping cluster names to ARNs, then allocating cost in proportion to bytes in. A daily Lambda writes Parquet results to S3 for Athena and Quick Sight. Enhanced Monitoring publishes per-topic CloudWatch metrics with little setup, but metric charges grow with topic-broker pairs. Open Monitoring exposes broker metrics at no additional charge; a Fargate scraper sends them to Amazon Managed Service for Prometheus, whose ingestion costs grow with samples. Both options use the same allocation logic. Bytes in is only a proxy: it misses retention, replication, compression, and consumer fan-out. Idle topics receive no row, so active topics may absorb the full cost; if no topics report traffic, the function splits cost evenly across configured topics. CUR can lag up to 24 hours, and metrics exist only after they are enabled. The method applies to Provisioned clusters; Serverless is out of scope.

### Source excerpt

Amazon MSK bills at the cluster level, with no per-topic breakdown. This post shows how to allocate shared MSK cluster costs to individual Kafka topics by combining AWS Cost and Usage Report billing with per-topic CloudWatch or Prometheus metrics, giving each team a usage-based view of its spend.

## A Lightweight, Open-Source Network Digital Twin Blueprint for IoT-Edge Environments

DevFeed: [A Lightweight, Open-Source Network Digital Twin Blueprint for IoT-Edge Environments](<https://devfeed.tech/articles/a-lightweight-open-source-network-digital-twin-blueprint-for-iot-edge-environments-127833.md>)

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

Author: Josevany do Amaral, Rute C. Sofia

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

Content type: tutorial

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [blueprint](<https://devfeed.tech/tags/blueprint.md>), [build](<https://devfeed.tech/tags/build.md>), [case](<https://devfeed.tech/tags/case.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [digital-twin](<https://devfeed.tech/tags/digital-twin.md>), [edge](<https://devfeed.tech/tags/edge.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [iot](<https://devfeed.tech/tags/iot.md>), [lightweight](<https://devfeed.tech/tags/lightweight.md>), [live](<https://devfeed.tech/tags/live.md>), [model](<https://devfeed.tech/tags/model.md>), [network](<https://devfeed.tech/tags/network.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-tools](<https://devfeed.tech/tags/open-tools.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [pitfalls](<https://devfeed.tech/tags/pitfalls.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>)

### AI overview

The tutorial presents a lightweight open-source blueprint for building Network Digital Twins in IoT-edge environments, using Containerlab, Open vSwitch, ONOS, and Prometheus/Grafana. It describes wireless impairment profiles--static, model-based, trace-driven, AI-generated, and live--and explains that each reproduces different aspects of wireless behavior. It also outlines a workflow for checking twin fidelity against a physical network, illustrated by a proof-of-concept Edge case study that reports pitfalls and lessons learned. The supplied abstract does not give implementation details or comparative results for the profile types.

### Source excerpt

arXiv:2606.24853v3 Announce Type: replace Abstract: IoT-Edge-Cloud infrastructures are increasingly heterogeneous, and experimenting across the continuum is difficult and risks disrupting live systems. Network Digital Twins (NDT) are a pragmatic answer, yet practitioners lack a structured account of three things: how to build an NDT from open tools, how to model wireless impairments, and how to understand whether the twin is faithful to the physical network, or not. This tutorial introduces NDT through the IRTF reference model and walks through a lightweight open-source blueprint built on Containerlab, Open vSwitch, \textit{Open Network Operating System (ONOS)}, and Prometheus/Grafana. It then explains how to define wireless impairment profiles (static, model-based, trace-driven, AI-generated, and live), and what each approach can and cannot reproduce. Finally, it presents a workflow to validate the twin against the physical network. A proof-of-concept Edge case study illustrates the procedure, including the pitfalls encountered and the lessons learned. Directions for future research are outlined.

## How Red Hat OpenShift 5 simplifies incident diagnosis with supervised AI

DevFeed: [How Red Hat OpenShift 5 simplifies incident diagnosis with supervised AI](<https://devfeed.tech/articles/how-red-hat-openshift-5-simplifies-incident-diagnosis-with-supervised-ai-129635.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/how-red-hat-openshift-5-simplifies-incident-diagnosis-supervised-ai>)

Author: Vanessa Martini

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

Content type: article

Language: en

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

Topics: [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>), [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [human-in-the-loop UX](<https://devfeed.tech/topics/human-in-the-loop-ux.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [data](<https://devfeed.tech/tags/data.md>), [diagnosis](<https://devfeed.tech/tags/diagnosis.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [incident](<https://devfeed.tech/tags/incident.md>), [language](<https://devfeed.tech/tags/language.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-5](<https://devfeed.tech/tags/openshift-5.md>), [platform](<https://devfeed.tech/tags/platform.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [security-governance](<https://devfeed.tech/tags/security-governance.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

OpenShift Lightspeed turns alert response into structured, human-reviewed investigation: it can correlate Prometheus metrics, pod logs, and installed OpenTelemetry traces into evidence, signals, and draft findings. On OpenShift 4.22+ with Lightspeed operator 1.1.5+, teams can also request Perses metric panels in natural language; with cluster observability operator 1.6, panels are marked AI-assisted and expose PromQL, time range, and source metrics for review. OpenShift 5 adds an opt-in technology preview that watches existing Alertmanager receivers, runs standard oc/kubectl diagnostics, and stages remediation for approval. It requires Lightspeed operator 2 and a configured tool-calling LLM; no default model ships. Changes require administrator approval, run in ephemeral RBAC-sandboxed environments, and are audited, with failed remediation halted and escalated. Model endpoint choice determines where data is processed; locally hosted models can support air-gapped use.

### Source excerpt

Prometheus metrics, traces, and logs are rarely missing in modern enterprise environments. Most platform teams already have plenty of telemetry at their disposal. The real bottleneck is the sheer volume of data a human must parse before taking meaningful action during an incident.On a busy cluster, this creates a familiar and exhausting pattern: an alert fires, an engineer opens 3 different consoles, brings up a Prometheus Query Language (PromQL) scratchpad, executes a log query, and spends 20 minutes debating whether the signal represents a genuine emergency or background noise. Alert fatigue

## Buoyant Releases Kinference: An Open Source Inference Control Plane for Kubernetes and vLLM

DevFeed: [Buoyant Releases Kinference: An Open Source Inference Control Plane for Kubernetes and vLLM](<https://devfeed.tech/articles/buoyant-releases-kinference-an-open-source-inference-control-plane-for-kubernetes-and-vllm-122073.md>)

Original publisher: [Read original article](<https://www.marktechpost.com/2026/11/07/buoyant-kinference-open-source-inference-control-plane-kubernetes-vllm/>)

Author: Michal Sutter

Published: 2026-11-07T08:16:33Z

Content type: release

Language: en

Sources: [MarkTechPost](<https://devfeed.tech/sources/marktechpost.md>)

Topics: [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Dynamo](<https://devfeed.tech/topics/dynamo.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Git](<https://devfeed.tech/topics/git.md>), [linkerd](<https://devfeed.tech/topics/linkerd.md>)

Tags: [accounting](<https://devfeed.tech/tags/accounting.md>), [admission](<https://devfeed.tech/tags/admission.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-shorts](<https://devfeed.tech/tags/ai-shorts.md>), [aliases](<https://devfeed.tech/tags/aliases.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [applications](<https://devfeed.tech/tags/applications.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [cache](<https://devfeed.tech/tags/cache.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [editors-pick](<https://devfeed.tech/tags/editors-pick.md>), [for-devs](<https://devfeed.tech/tags/for-devs.md>), [inference](<https://devfeed.tech/tags/inference.md>), [inference-control-plane](<https://devfeed.tech/tags/inference-control-plane.md>), [kinference](<https://devfeed.tech/tags/kinference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kv-cache](<https://devfeed.tech/tags/kv-cache.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [new-releases](<https://devfeed.tech/tags/new-releases.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [policies](<https://devfeed.tech/tags/policies.md>), [routing](<https://devfeed.tech/tags/routing.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [staff](<https://devfeed.tech/tags/staff.md>), [tech-news](<https://devfeed.tech/tags/tech-news.md>), [technology](<https://devfeed.tech/tags/technology.md>), [ttft](<https://devfeed.tech/tags/ttft.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

Kinference is an Apache 2.0 alpha control plane for routing requests across vLLM workers on Kubernetes. Its inference handler uses KV-cache events and engine metrics to choose endpoints; five Kubernetes CRDs configure routing rules, token limits, model aliases, provider fallback, and per-tenant metrics. Policies can account for tenant, model, GPU pool state, and semantic tags, and can reject requests when no permitted provider remains. In Buoyant's self-reported comparison with random Kubernetes Service routing, median TTFT fell from 6.88 s to 0.31 s on shared-prefix traffic, while prompts without shared prefixes showed no median TTFT gain. Peak goodput was about 7.4x higher on shared-prefix and 3.5x on multiturn traffic. The benchmark used three L40S GPUs per arm and offline-agent SLOs; it did not compare against cache-aware routers. The current release is v0.1.0-alpha.7, and rate limiting, classifiers, and Anthropic API support are listed as not yet shipped.

### Source excerpt

Buoyant has released Kinference, an Apache 2.0 inference control plane for vLLM on Kubernetes. It adds declarative routing policies, KV-cache-aware load balancing and per-tenant metrics, and cut median TTFT 95% in Buoyant's own benchmark. The post Buoyant Releases Kinference: An Open Source Inference Control Plane for Kubernetes and vLLM appeared first on MarkTechPost.

## MongoDB CDC connector for ClickPipes is now generally available

DevFeed: [MongoDB CDC connector for ClickPipes is now generally available](<https://devfeed.tech/articles/mongodb-cdc-connector-for-clickpipes-is-now-generally-available-117630.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/mongodb-cdc-connector-clickpipes-ga>)

Author: Marta Paes

Published: 2026-11-04T17:46:41Z

Content type: release

Language: en

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

Topics: [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>)

Tags: [cdc](<https://devfeed.tech/tags/cdc.md>), [lag](<https://devfeed.tech/tags/lag.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [resource](<https://devfeed.tech/tags/resource.md>), [structured](<https://devfeed.tech/tags/structured.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

MongoDB CDC ClickPipes is generally available for ClickHouse Cloud, using MongoDB Change Streams for near-real-time replication. GA adds automatic parallel snapshots partitioned by `_id`, with sampled boundaries to balance uneven collections. Structured ingestion is optional: it infers a schema and maps top-level fields to typed columns; unknown fields and type mismatches are retained in `_peerdb_malformed_data`. Deeper flattening is not yet supported. Users can configure target fields, partitioning, sorting keys, enable collection pre-images for deletes, or filter deletes to retain history. New CPU, memory, network, and source, destination, and end-to-end lag metrics are available in the UI and Prometheus endpoint. OpenAPI and Terraform management require Terraform v3.14.0 or later. Billing began November 4, 2026; the connector is available in all ClickHouse Cloud service tiers.

### Source excerpt

The MongoDB CDC connector for ClickPipes is now generally available, with parallel snapshotting, structured ingestion into typed columns, lag and resource metrics, and Terraform and OpenAPI support.

## GHOST Driver

DevFeed: [GHOST Driver](<https://devfeed.tech/articles/ghost-driver-116476.md>)

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

Author: Azhar Shaikh

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

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [eBPF](<https://devfeed.tech/topics/ebpf.md>), [gpu monitoring](<https://devfeed.tech/topics/gpu-monitoring.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [dma](<https://devfeed.tech/topics/dma.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [dmaengine](<https://devfeed.tech/topics/dmaengine.md>)

Tags: [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-os](<https://devfeed.tech/tags/cs-os.md>), [dma](<https://devfeed.tech/tags/dma.md>), [driver](<https://devfeed.tech/tags/driver.md>), [drm](<https://devfeed.tech/tags/drm.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-clusters](<https://devfeed.tech/tags/gpu-clusters.md>), [gpu-utilization](<https://devfeed.tech/tags/gpu-utilization.md>), [interrupt](<https://devfeed.tech/tags/interrupt.md>), [latency](<https://devfeed.tech/tags/latency.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [mig](<https://devfeed.tech/tags/mig.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [profiling](<https://devfeed.tech/tags/profiling.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [vgpu](<https://devfeed.tech/tags/vgpu.md>)

### AI overview

GHOST-Driver aims to explain why high GPU utilization readings can coexist with lower effective throughput by tracing delays inside the Linux kernel driver, which userspace tools such as CUPTI do not expose. The eBPF framework follows six submission stages, from ioctl entry and GEM buffer validation through fence handling, command emission, DMA scheduling, and interrupt signaling. It correlates traces with tenant vGPU context IDs for attribution in SR-IOV and MIG environments and exports metrics to Prometheus and OpenTelemetry. The abstract reports sub-microsecond resolution and CPU overhead below 2% in production.

### Source excerpt

arXiv:2611.03649v1 Announce Type: cross Abstract: AI inference workloads running on GPU clusters exhibit a well-documented utilization paradox: monitoring tools such as nvidia-smi regularly report GPU utilization figures above 80%, yet effective compute throughput is substantially lower. A significant fraction of reported utilization time is consumed by fence waits, driver submission overhead, DMA scheduling latency, and interrupt coalescing delays, none of which is visible to userspace profiling tools. These hidden latency components are embedded deep inside the Linux kernel GPU driver stack, primarily within the Direct Rendering Manager (DRM) subsystem, GEM buffer object lifecycle, and dma_fence synchronization infrastructure. Existing vendor profiling tools like CUPTI operate at the CUDA userspace boundary and provide no visibility into kernel-side driver paths. We present GHOST-Driver (GPU Host-Side Observability and Tracing for Drivers), a non-intrusive eBPF-based framework that attaches to stable DRM kernel tracepoints and select kprobes to expose the full latency decomposition of the GPU driver submission path with sub-microsecond resolution and CPU overhead below 2% in production. GHOST-Driver tracks six key submission stages (ioctl entry, GEM BO validation, dma_fence dependency resolution, command ring emission, DMA engine scheduling, and interrupt fence signaling) and correlates them with per-tenant vGPU context IDs for multi-tenant attribution in SR-IOV and MIG environments, exporting trace metrics to Prometheus and OpenTelemetry.

## What's new in ClickStack - September and October '26

DevFeed: [What's new in ClickStack - September and October '26](<https://devfeed.tech/articles/what-s-new-in-clickstack-september-and-october-26-115492.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/whats-new-in-clickstack-october-2026>)

Author: The ClickStack Team

Published: 2026-11-03T19:09:52Z

Content type: release

Language: en

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

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [timezone](<https://devfeed.tech/topics/timezone.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [added](<https://devfeed.tech/tags/added.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [collector](<https://devfeed.tech/tags/collector.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [explorer](<https://devfeed.tech/tags/explorer.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [list](<https://devfeed.tech/tags/list.md>), [logs](<https://devfeed.tech/tags/logs.md>), [october](<https://devfeed.tech/tags/october.md>), [query](<https://devfeed.tech/tags/query.md>), [releases](<https://devfeed.tech/tags/releases.md>), [search](<https://devfeed.tech/tags/search.md>), [trace](<https://devfeed.tech/tags/trace.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [type](<https://devfeed.tech/tags/type.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

ClickStack v2.39-v2.42 added interactive ad hoc dashboard filters, expanded PromQL across chart types and the dashboards API, and query attribution that identifies the ClickStack surface responsible for ClickHouse load. Dashboard updates include required and single-select variables, saved relative time ranges, and PromQL heatmap modes; PromQL remains experimental and requires enablement, with ClickHouse 26.8 or newer recommended for self-managed servers. Search, trace, and alert workflows gained filtering, trace logs, chart-explorer alerts, and richer webhook validation and templates. The collector now offers opt-in StatsD and span-metrics components configured through a custom pipeline. For authenticated self-hosted deployments, upgrades require explicitly setting EXPRESS_SESSION_SECRET.

### Source excerpt

The September and October ClickStack releases bring ad hoc dashboard filters, PromQL for every chart type, ClickStack query tracing, a Trace logs tab, alerts from the chart explorer, and a long list of search page and collector improvements.

## Alerting in the Debezium Platform

DevFeed: [Alerting in the Debezium Platform](<https://devfeed.tech/articles/alerting-in-the-debezium-platform-113311.md>)

Original publisher: [Read original article](<https://debezium.io/blog/2026/11/02/alerting-in-the-debezium-platform/>)

Author: Indra Raj Shukla

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

Content type: news

Language: en

Sources: [Debezium](<https://devfeed.tech/sources/debezium-io.md>)

Topics: [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [backend](<https://devfeed.tech/tags/backend.md>), [badge](<https://devfeed.tech/tags/badge.md>), [channel](<https://devfeed.tech/tags/channel.md>), [collector](<https://devfeed.tech/tags/collector.md>), [debezium](<https://devfeed.tech/tags/debezium.md>), [lag](<https://devfeed.tech/tags/lag.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [platform](<https://devfeed.tech/tags/platform.md>), [queue](<https://devfeed.tech/tags/queue.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>)

### AI overview

Debezium Management Platform alert rules apply comparisons and thresholds to monitoring panels and evaluate globally, creating a separate incident for each pipeline that breaches a rule, including pipelines added later. Rules choose a panel, a reduction function (`last`, `avg`, `min`, `max`, or `sum`), a comparison and threshold, a hold duration, severity, and optional notification channels. The Platform evaluates enabled rules every 60 seconds by default; each firing and resolution sends one notification, with no repeats while an alert remains active. Alerts always appear in the UI. Optional reusable email and webhook channels support test notifications; webhooks send a versioned payload for both firing and resolved states. The Events page lists incidents, while a header badge counts active Critical and Warning alerts; Info alerts are excluded. Resolved incidents are removed after a default 30-day retention period, while firing incidents are retained.

### Source excerpt

The Debezium Management Platform has been able to show you how your pipelines are doing for a while now. The monitoring dashboard tells you the event rate, the source lag, the queue utilization, whether the snapshot finished, and so on. But it is passive as it only helps while somebody is looking at it. In his mid-year Platform update, Mario listed alerting as one of the next things we wanted to tackle. That work has now landed. The Platform can now watch those same panels for you and tell you when one of them crosses a line you care about. This post walks through what alerting looks like in the Platform, how a rule is defined, where notifications go, how an alert moves from quiet to firing, and where to review it all afterwards. Read more...

## Blog: Falco 0.45.2: security updates and a look back at 0.45.1

DevFeed: [Blog: Falco 0.45.2: security updates and a look back at 0.45.1](<https://devfeed.tech/articles/blog-falco-0-45-2-security-updates-and-a-look-back-at-0-45-1-110695.md>)

Original publisher: [Read original article](<https://falco.org/blog/falco-0-45-2/>)

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

Content type: release

Language: en

Sources: [Falco](<https://devfeed.tech/sources/falco-falco.md>)

Topics: [Falco](<https://devfeed.tech/topics/falco.md>), [Security](<https://devfeed.tech/topics/security.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [blog](<https://devfeed.tech/tags/blog.md>), [buster](<https://devfeed.tech/tags/buster.md>), [ca](<https://devfeed.tech/tags/ca.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [clients](<https://devfeed.tech/tags/clients.md>), [community](<https://devfeed.tech/tags/community.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [crash](<https://devfeed.tech/tags/crash.md>), [custom](<https://devfeed.tech/tags/custom.md>), [debian](<https://devfeed.tech/tags/debian.md>), [falco](<https://devfeed.tech/tags/falco.md>), [release](<https://devfeed.tech/tags/release.md>), [security](<https://devfeed.tech/tags/security.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Falco 0.45.2 updates CA trust stores in its Wolfi and Debian images and driver-loader images to address the eMudhra intermediate CA compromise; DEB/RPM users and deployments with custom CA bundles must update those separately. It also includes Falcoctl 0.14.3, container plugin 0.7.6, and OpenSSL 3.5.9 LTS. OpenSSL's default TLS security level is now 2, requiring RSA, DSA, and DH keys of at least 2048 bits and elliptic-curve keys of at least 224 bits; weaker legacy HTTPS endpoints may fail to connect. The release includes 0.45.1 reliability fixes for a Prometheus scrape race, file output recovery with keep_alive (the failed alert is not replayed), reloads when watched files disappear, and package installation on hosts without modern eBPF support. Separately deployed Falcosidekick needs its own update to 2.35.1 for trust and Go security updates. Helm chart 9.2.2 defaults to Falco 0.45.2 and related component versions; review explicit image or plugin version pins.

### Source excerpt

Hey Falco community, Falco 0.45.2 is available! This patch brings certificate trust updates and newer security dependencies, alongside the reliability fixes delivered in 0.45.1. Since we did not publish a separate announcement for 0.45.1, let's catch up on both releases here. If you are running 0.45.0 or 0.45.1, we recommend upgrading to 0.45.2. And if you are heading to KubeCon in Salt Lake City, we would love to meet you there! The main focus of 0.45.2 is the response to the eMudhra intermediate CA compromise. Clients that still trust the affected certificate chains can accept certificates used to impersonate HTTPS services. Updating the trust stores used by those clients is part of addressing that risk. We refreshed the CA trust stores in both the default Wolfi and Debian Falco images, along with the driver-loader images. The Buster driver loader remains available, with its trust store corrected as well. The release also bundles Falcoctl 0.14.3 and the container plugin 0.7.6, incorporating upstream Go security updates. See the packaging changes for details. For installations using DEB or RPM packages, please apply your distribution's CA certificate updates too. If your deployment supplies a custom CA bundle, make sure that bundle is updated as well. We also updated the bundled OpenSSL to 3.5.9 LTS. There is a compatibility change to keep in mind: its default TLS security level is now 2. RSA, DSA, and DH keys must be at least 2048 bits, and elliptic-curve keys at least 224 bits. Check legacy HTTPS endpoints before upgrading, since weaker keys or parameters can cause TLS connections to fail. The OpenSSL update includes the details. The fixes from 0.45.1 are included too. They address several problems that can interrupt a running Falco deployment or make upgrades harder: Prometheus metrics: fixed a race that could crash Falco when a metrics scrape overlapped with event processing. Details. File output: with keep_alive: true, Falco now reports a failed write and atte

## Positive alerts in Prometheus

DevFeed: [Positive alerts in Prometheus](<https://devfeed.tech/articles/positive-alerts-in-prometheus-100749.md>)

Original publisher: [Read original article](<https://alexwlchan.net/2026/positive-alerts/>)

Published: 2026-10-26T18:38:45Z

Content type: article

Language: en

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

Topics: [Prometheus alert rules](<https://devfeed.tech/topics/prometheus-alert-rules.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [alertmanager](<https://devfeed.tech/tags/alertmanager.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [computers-and-code](<https://devfeed.tech/tags/computers-and-code.md>), [database](<https://devfeed.tech/tags/database.md>), [exception](<https://devfeed.tech/tags/exception.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [noise](<https://devfeed.tech/tags/noise.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

### AI overview

The example avoids repeated notifications from a flapping scrape alert while keeping track of when its exception can be removed. The original rule fires when the average `up` value over 30 minutes falls below 0.95 for an hour. The team excluded the overloaded service from that rule and added a positive alert for that service when the same average stayed at or above 0.95 for 14 days. When the recovery alert fired, they removed the exception. This gave them a recovery signal without relying on a fixed-duration Alertmanager Silence, which could expire before the service was fixed or remain after it recovered.

### Source excerpt

When we create an exception to an alert, we can use a second alert to tell us when the exception no longer applies.

## AI Root Cause Analysis: Architecture, Testing, and Evaluation

DevFeed: [AI Root Cause Analysis: Architecture, Testing, and Evaluation](<https://devfeed.tech/articles/ai-root-cause-analysis-architecture-testing-and-evaluation-109738.md>)

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

Author: Ales Justin

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

Content type: article

Language: en

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

Topics: [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [langchain4j](<https://devfeed.tech/topics/langchain4j.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [langchain4j](<https://devfeed.tech/tags/langchain4j.md>), [lgtm](<https://devfeed.tech/tags/lgtm.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-as-judge](<https://devfeed.tech/tags/llm-as-judge.md>), [logs](<https://devfeed.tech/tags/logs.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

AI Root Cause Analysis correlates traces, logs, and point-in-time Prometheus metrics through an LLM that autonomously selects telemetry tools and builds a structured report. OpenTelemetry-instrumented applications connect through an LGTM stack via MCP; optional Quarkus Dev MCP supports source examination and dashboard generation. A filtering layer strips SDK noise, redundant fields, and low-signal metrics (586 entries to about 35) to limit context use. Chaos tests inject application and network failures, including database and weather API faults via Toxiproxy, then score reports with a separate judge LLM on four dimensions (25 points each); the default passing threshold is 70/100 and can be overridden. Analyzer and scorer can use different providers to reduce self-evaluation bias. The excerpt reports 19 scenarios passing across provider combinations.

### Source excerpt

In the introductory post, we showed what AI Root Cause Analysis does and how to get started. This post goes deeper -- into the architecture, the analysis pipeline, how we keep telemetry data within LLM context limits, and how we test analysis quality using chaos engineering with LLM-as-judge evaluation. Architecture The system has a layered architecture connecting monitored applications to the AI analysis engine through an observability stack: Your applications just need OpenTelemetry instrumentation -- no code changes required. The AI module connects to your existing LGTM stack via MCP and optionally to your running Quarkus applications via Quarkus Dev MCP for source examination and dashboard generation. The AI module uses LangChain4j @RegisterAiService interfaces backed by a ~290-line system prompt that instructs the LLM on three-way telemetry correlation, chaos detection patterns, severity classification, and structured output formatting. Five tools are exposed to the LLM during analysis: Tool What It Provides provideLastNTraceIds Recent trace IDs from Tempo (TraceQL) traceById Full trace data for a specific trace logsWithTraceId Correlated Loki logs for a trace getRootSpanStartTime Timestamp for metric queries getAllMetricsForDatetime Prometheus metrics at a point in time The LLM orchestrates these tools autonomously -- it decides which traces look interesting, pulls their logs, checks metrics, and builds the analysis iteratively. The Analysis Pipeline When you hit GET /analyze/{n}, the following sequence unfolds: Tool dispatch -- The AI module sends the system prompt and tool definitions to the LLM Trace retrieval -- The LLM calls provideLastNTraceIds to get the N most recent traces Per-trace investigation -- For each trace, the LLM pulls full trace data and correlated logs through StripMcpClient, which strips SDK noise, localhost attributes, and redundant fields Metrics context -- The LLM queries Prometheus metrics at the root span's start time; the filtering layer r

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

## Postgres wait events, now in Query Insights

DevFeed: [Postgres wait events, now in Query Insights](<https://devfeed.tech/articles/postgres-wait-events-now-in-query-insights-89996.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/postgres-wait-events-query-insights>)

Author: Amog Iska

Published: 2026-10-19T11:15:28Z

Content type: release

Language: en

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

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Deadlock](<https://devfeed.tech/topics/deadlock.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [grafana](<https://devfeed.tech/tags/grafana.md>), [latency](<https://devfeed.tech/tags/latency.md>), [locks](<https://devfeed.tech/tags/locks.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>)

### AI overview

ClickHouse Managed Postgres Query Insights now reports wait event metrics, showing what active sessions are waiting on and how wait categories contribute to database load. It adds blocked-session and lock-wait charts, and exposes query, resource, and wait metrics through Prometheus for dashboards and alerting.

### Source excerpt

Query Insights for ClickHouse Managed Postgres now shows what active sessions are waiting on, with wait event breakdowns, blocked-session and lock-wait charts, and the same metrics in Prometheus.

## Dynatrace Release Radar 09.26

DevFeed: [Dynatrace Release Radar 09.26](<https://devfeed.tech/articles/dynatrace-release-radar-09-26-88075.md>)

Original publisher: [Read original article](<https://www.dynatrace.com/news/blog/dynatrace-release-radar-09-26/>)

Author: Michael Winkler

Published: 2026-10-15T15:59:29Z

Content type: release

Language: en

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

Topics: [dynatrace](<https://devfeed.tech/topics/dynatrace.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [dynatrace](<https://devfeed.tech/tags/dynatrace.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [release](<https://devfeed.tech/tags/release.md>), [release-radar](<https://devfeed.tech/tags/release-radar.md>)

### AI overview

Dynatrace's September release updates add service backtraces from database statements, guided onboarding through QuickStart, and AI-assisted findings. The release also improves trace investigation by preserving chart and filter context, and expands host monitoring through OpenTelemetry Collector setup and visibility in Infrastructure & Operations.

### Source excerpt

This series covers recent Dynatrace releases and updates, focusing on what's new, what's changed, and how these enhancements can benefit you and your organization. This edition covers the capabilities rolled out in September. If you want to see September in action, head over to our Release Radar launchpad on the Dynatrace Playground. Trace database statements [...] The post Dynatrace Release Radar 09.26 appeared first on Dynatrace news.

## From Backup to Assurance: Monitoring Veeam with Zabbix

DevFeed: [From Backup to Assurance: Monitoring Veeam with Zabbix](<https://devfeed.tech/articles/from-backup-to-assurance-monitoring-veeam-with-zabbix-86671.md>)

Original publisher: [Read original article](<https://blog.zabbix.com/from-backup-to-assurance-monitoring-veeam-with-zabbix/33694/>)

Author: Michael Kammer

Published: 2026-10-14T08:16:23Z

Content type: article

Language: en

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

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [quickly](<https://devfeed.tech/tags/quickly.md>), [security](<https://devfeed.tech/tags/security.md>), [technical](<https://devfeed.tech/tags/technical.md>), [veeam](<https://devfeed.tech/tags/veeam.md>), [zabbix](<https://devfeed.tech/tags/zabbix.md>)

### AI overview

The article describes Zabbix integrations for monitoring Veeam Backup & Replication and Veeam Backup Enterprise Manager. They let IT teams track backup jobs, repository capacity, infrastructure health, and security events, and receive alerts about problems. The Enterprise Manager integration uses its REST API to consolidate monitoring across multiple deployments.

### Source excerpt

Your data isn't truly protected if you don't know when that protection fails. Today's organizations depend on backup infrastructure to safeguard critical workloads, yet a single backup failure, dwindling repository capacity, expired license, security incident, or infrastructure issue can quietly undermine that protection. The key isn't just having backups - it's knowing, as quickly and [...] The post From Backup to Assurance: Monitoring Veeam with Zabbix appeared first on Zabbix Blog.

## Meshery: Open-source cloud-native manager for Kubernetes

DevFeed: [Meshery: Open-source cloud-native manager for Kubernetes](<https://devfeed.tech/articles/meshery-open-source-cloud-native-manager-for-kubernetes-86433.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/14/meshery-open-source-cloud-native-manager-kubernetes/>)

Author: Anamarija Pogorelec

Published: 2026-10-14T05:00:01Z

Content type: article

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Cloud Native Ecosystem](<https://devfeed.tech/topics/cloud-native-ecosystem.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [github](<https://devfeed.tech/tags/github.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [security](<https://devfeed.tech/tags/security.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Meshery is an open-source tool for designing, validating, deploying, and managing Kubernetes infrastructure through a visual canvas and central console. It can run Kubernetes dry-run checks, integrate those checks into CI/CD pipelines, display infrastructure relationships, and share snapshots in GitHub pull requests. It also supports load testing and performance comparisons, with metrics from Prometheus and dashboards from Grafana.

### Source excerpt

Meshery is an open-source tool for designing, deploying and managing Kubernetes infrastructure, built by Layer5 and its community and hosted as a Cloud Native Computing Foundation project. Teams use it to lay out clusters and applications on a visual canvas, check the design, and push it to multiple clusters and clouds from one central console, without hand-editing YAML. Kubernetes runs on configuration files, and one wrong field or mismatched API version can sink a deployment. ... More -> The post Meshery: Open-source cloud-native manager for Kubernetes appeared first on Help Net Security.

## Oxynote: Self-Hosted Wiki with Live Metrics (Docker Guide)

DevFeed: [Oxynote: Self-Hosted Wiki with Live Metrics (Docker Guide)](<https://devfeed.tech/articles/oxynote-self-hosted-wiki-with-live-metrics-docker-guide-86292.md>)

Original publisher: [Read original article](<https://noted.lol/oxynote-self-hosted-wiki-docker/>)

Author: David Bykovas

Published: 2026-10-13T13:29:49Z

Content type: tutorial

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [Wiki](<https://devfeed.tech/topics/wiki.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [docker](<https://devfeed.tech/tags/docker.md>), [guide](<https://devfeed.tech/tags/guide.md>), [integration](<https://devfeed.tech/tags/integration.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-wikis](<https://devfeed.tech/tags/self-hosted-wikis.md>)

### AI overview

This guide explains how engineering teams can run Oxynote, an open-source self-hosted wiki, with Docker. It covers setup, connecting Prometheus and SQL data sources, adding live charts to pages, reviewing documentation changes, and optionally connecting AI tools through MCP.

### Source excerpt

Oxynote is an open-source, self-hosted wiki built for engineering teams. This guest guide covers Docker installation and its live metrics integration.

## Building a Unified Observability Platform on GreptimeDB: A Reference Architecture

DevFeed: [Building a Unified Observability Platform on GreptimeDB: A Reference Architecture](<https://devfeed.tech/articles/building-a-unified-observability-platform-on-greptimedb-a-reference-architecture-65202.md>)

Original publisher: [Read original article](<https://blog.devops.dev/building-a-unified-observability-platform-on-greptimedb-a-reference-architecture-35c754365411?source=rss----33f8b2d9a328---4>)

Author: Greptime

Published: 2026-10-05T20:11:01Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [article](<https://devfeed.tech/tags/article.md>), [astronomy](<https://devfeed.tech/tags/astronomy.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [collectors](<https://devfeed.tech/tags/collectors.md>), [components](<https://devfeed.tech/tags/components.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [demo](<https://devfeed.tech/tags/demo.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [devops](<https://devfeed.tech/tags/devops.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [incident](<https://devfeed.tech/tags/incident.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [jaeger](<https://devfeed.tech/tags/jaeger.md>), [large](<https://devfeed.tech/tags/large.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-demo](<https://devfeed.tech/tags/opentelemetry-demo.md>), [platform](<https://devfeed.tech/tags/platform.md>), [reference-architecture](<https://devfeed.tech/tags/reference-architecture.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

The architecture routes metrics, logs, and traces into one GreptimeDB while leaving collectors in place: dashboards and alerts use PromQL, and investigation and long-range analysis use SQL. The excerpt describes protocol endpoints, per-signal table and indexing choices, and three deployment tiers. Flow can maintain small aggregate tables for dashboards and alerts; frontend groups isolate query handling, while storage isolation through Read Replicas or Datanode groups is Enterprise-only. Object storage supports longer retention; Local WAL suits standalone and small clusters, while Remote WAL uses Kafka for faster recovery. Migration is described as dual-write, switch reads, then retire the old system. Compatibility has limits: Loki writes are supported but LogQL queries move to SQL; open-source Elasticsearch support covers bulk writes, not Query DSL. The article also reports better agent-diagnosis results on GreptimeDB, while cautioning that its comparison changed the full interface bundle and does not isolate the storage engine's contribution.

### Source excerpt

This article assumes you have already decided to put metrics, logs, and traces into one database. Why unify, and why now, is covered in our earlier post on the history of observability unification. This one covers what comes after that decision: which components to deploy, how data flows, which decisions are still yours to make, and what the topology looks like at three scales: standalone, small cluster, and large cluster. The architecture fits in one sentence: leave the collectors alone and point them at one GreptimeDB; dashboards and alerts go through PromQL, incident investigation and long-range analysis through SQL. The validation environment is the official OpenTelemetry Astronomy Shop demo: 14 services, SDKs in several languages, and a default backend of Jaeger, OpenSearch, and Prometheus. We replaced those three with a single GreptimeDB v1.2.0 standalone instance, plus a node_exporter and a Prometheus that only scrapes. The configuration, table schemas, query results, and incident records in this article come from that environment; the complete setup is in the greptimedb-observability-playground repository. Enterprise-only features are marked where they come up. Three workloads the platform has to carry Dashboards and alerts. Grafana panels refresh every few seconds and alert rules evaluate every minute, over the last few minutes to few hours of data. Many queries, each small, each latency-sensitive. Incident investigation. One investigation moves between metrics, logs, and traces: from an alert to the slow service, from the service to the slow call chain, from the call chain to the error logs and node resources of that time window. The queries are exploratory; nobody knows in advance how many there will be, and humans are no longer the only ones issuing them. In our Agent RCA Bench, one agent investigation averaged thirty to forty tool calls, with some approaching fifty. Long-range analysis. Capacity planning, weekly reports, cost attribution: scans over wee

## Introducing Solana Microscope: Program Monitoring and Alerts

DevFeed: [Introducing Solana Microscope: Program Monitoring and Alerts](<https://devfeed.tech/articles/introducing-solana-microscope-program-monitoring-and-alerts-66891.md>)

Original publisher: [Read original article](<https://solana.com/news/solana-microscope>)

Author: Jo Desormeaux

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

Content type: release

Language: en

Sources: [Solana News Feed](<https://devfeed.tech/sources/solana-news-feed.md>)

Topics: [Solana](<https://devfeed.tech/topics/solana.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [blockchain-technology](<https://devfeed.tech/tags/blockchain-technology.md>), [crypto-news](<https://devfeed.tech/tags/crypto-news.md>), [cryptocurrency](<https://devfeed.tech/tags/cryptocurrency.md>), [defi](<https://devfeed.tech/tags/defi.md>), [developers](<https://devfeed.tech/tags/developers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [nfts](<https://devfeed.tech/tags/nfts.md>), [podcasts](<https://devfeed.tech/tags/podcasts.md>), [solana](<https://devfeed.tech/tags/solana.md>), [solana-ecosystem](<https://devfeed.tech/tags/solana-ecosystem.md>), [web3](<https://devfeed.tech/tags/web3.md>)

### AI overview

Microscope is an open-source, self-hosted monitoring and alerting tool for Solana programs. It decodes instructions, events, and optional Squads multisig activity into Grafana dashboards and alerts, while monitoring the health of its own data pipeline. Teams can deploy it with Docker Compose, on AWS or GCP, or alongside existing Grafana Cloud infrastructure.

### Source excerpt

Microscope decodes Solana program and Squads multisig activity into Grafana dashboards and alerts for Slack, Telegram, and PagerDuty.

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