GitLab vs Grafana Labs

10-Q Financial Filing Analysis for GitLab (2026-09-02)

Im zweiten Quartal zum 31. Juli 2026 erzielte GitLab einen Gesamtumsatz von 286,3 Mio. USD, was einem Wachstum von 21 % im Vergleich zum Vorjahresquartal (235,96 Mio. USD) entspricht. Getragen wurde dieses Wachstum von den Abonnements (Self-Managed und SaaS), die um 21 % auf 258,3 Mio. USD zulegten, sowie einem Anstieg der Großkunden mit über 100.000 USD ARR auf 1.571 (ein Plus von 17 % YoY). Die Dollar-Based Net Retention Rate lag bei 117 %. Trotz des Umsatzanstiegs weitete sich der GAAP-Betriebsverlust auf 56,9 Mio. USD aus (Vorjahr: 18,4 Mio. USD), was vor allem auf gestiegene Hosting-Kosten, aktienbasierte Vergütungen von 75,0 Mio. USD sowie Restrukturierungskosten von 23,3 Mio. USD im Rahmen des „2027 Plan“ (Umfang: ca. 14 % der Belegschaft) zurückzuführen ist. Der Nettoverlust belief sich auf 36,8 Mio. USD bzw. $(0,22) pro Aktie.

• Der Umsatz im 2. Quartal 2026 stieg im Jahresvergleich um 21 % auf 286,3 Mio. USD, während der Sechsmonatsumsatz 550,4 Mio. USD erreichte (ein Plus von 22 %).
• Die Zahl der Großkunden mit mehr als 100.000 USD ARR stieg um 17 % auf 1.571, bei einer Net Retention Rate von 117 %.
• GitLab leitete den Restrukturierungsplan '2027 Plan' ein, der ca. 14 % der Belegschaft betrifft und im Quartal Restrukturierungsaufwendungen in Höhe von 23,3 Mio. USD verursachte (Gesamterwartung: 30 bis 35 Mio. USD).

GitLab 19.4 Brings New Agentic Automation at a Lower Cost

GitLab 19.4 release announced, bringing new agentic automation at a lower cost. Also, GitLab reported Q2 FY2027 financial results and scaled agentic AI across trusted software delivery workflows.

GitLab Scales Agentic AI Across Trusted Software Delivery Workflows

New press release (August 20, 2026) announcing GitLab's expansion of agentic AI across trusted software delivery workflows.

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.

Read-Only SRE: Using AI in Production Safely

The author argues for a conservative, observation-first role for AI in production SRE workflows: grant AI read-only access to telemetry (logs, dashboards, events, commits, deployment history, IaC plans) so it can synthesize incident timelines, summarize recent activity, and surface anomalies — but keep production write actions (restarts, scaling, Terraform changes, firewall edits) under human control. The piece frames AI as a fast, always-available “SRE intern” that helps engineers think faster without taking ownership of risky changes. The author acknowledges AI may earn broader operational responsibilities in the future but recommends an onboarding approach that mirrors human engineers: observe, learn, and prove understanding before receiving write permissions. Published on dev.to on 2026-07-10.

• Author recommends giving AI read-only access to production telemetry (logs, events, monitoring dashboards, deployment history, Terraform plans, Git commits) to help with incident troubleshooting.
• Author explicitly advises against allowing AI to perform production writes (restarts, scaling, deleting resources, changing Terraform, updating firewall rules) due to accountability and business-context gaps.
• Author frames AI as a fast 'SRE intern' useful for preparing incident timelines, summarizing dashboards, highlighting anomalies and suggesting possible causes without making changes.