ClickHouse vs Grafana Labs

ClickHouse expands collaboration with Microsoft, bringing Fabric integration, deeper OneLake interoperability, and enterprise deployment flexibility

ClickHouse announced a significant expansion of its strategic collaboration with Microsoft at The European Microsoft Fabric + SQL Community Conference in Barcelona on September 29, 2026. The expansion includes the public preview of the ClickHouse workload for Microsoft Fabric, general availability of OneLake read, public preview of OneLake write, and availability of ClickHouse Bring Your Own Cloud (BYOC) in the Microsoft Marketplace. These capabilities aim to enable sub-second analytics on OneLake data and provide enterprise deployment flexibility without data duplication.

• ClickHouse announced the expanded Microsoft collaboration on September 29, 2026 at The European Microsoft Fabric + SQL Community Conference in Barcelona.
• The ClickHouse workload for Microsoft Fabric is now available in public preview through the Fabric workload hub.
• ClickHouse support for reading Apache Iceberg tables from OneLake using OneLake Table APIs is now generally available.

ClickHouse expands collaboration with Microsoft, bringing Fabric integration, deeper OneLake interoperability, and enterprise deployment flexibility

On September 29, 2026, at The European Microsoft Fabric + SQL Community Conference in Barcelona, ClickHouse announced an expanded strategic collaboration with Microsoft. The announcement includes the public preview of the native ClickHouse workload for Microsoft Fabric, general availability of OneLake read, public preview of OneLake write, and availability of ClickHouse BYOC in the Microsoft Marketplace. These capabilities let joint customers query OneLake data at sub-second speeds without copying data, while BYOC provides managed ClickHouse Cloud inside a customer's Azure tenant with procurement via Microsoft agreements.

• On September 29, 2026, ClickHouse announced the expanded collaboration with Microsoft at The European Microsoft Fabric + SQL Community Conference in Barcelona.
• The native ClickHouse workload for Microsoft Fabric is now available in public preview through the Fabric workload hub, enabling sub-second analytics on OneLake queries.
• ClickHouse support for reading Apache Iceberg tables from OneLake using OneLake Table APIs is generally available; writing Iceberg tables to OneLake is in public preview.

ClickHouse appoints Mike Scarpelli, former Snowflake and ServiceNow CFO, to Board of Directors

ClickHouse, a leader in real-time analytics, data warehousing, observability, and AI/ML, today announced the appointment of Michael Scarpelli to its Board of Directors.

Tempo 3.1 release: new features for Kafka, TraceQL metrics updates, trace redaction, and more

Grafana Labs blog features a new post on Tempo 3.1 release with new features for Kafka, TraceQL metrics updates, trace redaction, and more.

Observability Stack: Prometheus, Node Exporter, Grafana

A technical how-to explaining the three-piece observability stack: Prometheus (time-series database that scrapes metrics), Node Exporter (exposes OS-level metrics at a /metrics HTTP endpoint), and Grafana (visualizes Prometheus data as dashboards). The article describes the pull-based model Prometheus uses, the role of Node Exporter as a translator of OS stats, how Grafana queries Prometheus, default ports (Prometheus 9090, Node Exporter 9100, Grafana 3000), basic install commands, a sample prometheus.yml with scrape_interval and job_name, and next steps such as adding scrape targets, writing PromQL queries, and adding Alertmanager for notifications.

• Prometheus is a time-series database and monitoring system that scrapes metrics from HTTP endpoints and exposes its own metrics on port 9090.
• Node Exporter exposes hardware and OS-level metrics at a /metrics endpoint (default port 9100) and is typically installed one-per-machine.
• Grafana queries Prometheus (e.g., via PromQL) to render dashboards and runs by default on port 3000; it stores no metrics itself.

Building an Internal Developer Platform on Azure AKS

This technical article explains how to create an Internal Developer Platform (IDP) using Azure Kubernetes Service (AKS). It outlines core components including AKS as the managed Kubernetes backbone, a service mesh (e.g., Istio or Linkerd) for microservice communication, CI/CD pipelines (Azure DevOps, GitHub Actions, Jenkins) for automated build and deployment, monitoring and logging tools (Azure Monitor, Prometheus, Grafana, Azure Log Analytics), and security/compliance controls (RBAC, Pod Security Policies, Azure Policy, Azure Security Center). The piece describes an example developer workflow from code push to production and summarizes benefits such as increased efficiency, scalability, security, and consistency.

• An Internal Developer Platform (IDP) is a set of tools, processes, and automations that simplifies development, testing, and deployment for developers.
• Azure Kubernetes Service (AKS) is presented as the central managed Kubernetes environment where containerized applications run.
• Service meshes such as Istio or Linkerd are recommended to manage microservice communication, including load balancing, traffic management, and security policies.