Grafana Labs vs PagerDuty

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.

8-K Financial Filing Analysis for PagerDuty (2026-08-27)

On August 26, 2026, PagerDuty, Inc. announced a significant restructuring initiative aimed at improving operational efficiency and realigning resources toward strategic priorities. As part of this global scaling plan, the enterprise SaaS company is reducing its current headcount by approximately 15%. PagerDuty estimates it will incur non-recurring pre-tax restructuring charges ranging from $5.5 million to $7.5 million, consisting primarily of severance payments, notice pay, employee benefits, and related exit costs. The company anticipates incurring the majority of these charges in the third quarter of fiscal 2027, with implementation and cash outlays largely completed by the end of the fourth quarter of fiscal 2027.

• Workforce reduction of approximately 15% across global operations announced on August 26, 2026.
• Estimated non-recurring restructuring charges between $5.5 million and $7.5 million, primarily for severance and employee benefits.
• Implementation and cash payments expected to be substantially complete by the end of Q4 fiscal 2027, with the majority of charges incurred in Q3 fiscal 2027.

10-Q Financial Filing Analysis for PagerDuty (2026-08-27)

PagerDuty reported its Q2 fiscal 2027 results for the quarter ended July 31, 2026, delivering total revenue of $124.4 million, up 0.8% year-over-year. Operating income expanded significantly to $10.2 million from $3.6 million in Q2 fiscal 2026, driven by disciplined cost containment as total operating expenses dropped 6.6% to $94.2 million. GAAP net income attributable to PagerDuty reached $7.8 million ($4.7 million attributable to common stockholders), supported by sustained gross margins of 83.9% and strong operating cash flows of $81.2 million for the first half of the fiscal year. Concurrently, PagerDuty disclosed a strategic restructuring plan announced in August 2026 involving a 15% workforce reduction to enhance operational agility and realign resources around AI-driven operations and agentic workflows, resulting in estimated pre-tax charges of $5.5 million to $7.5 million primarily in Q3 fiscal 2027.

• Q2 fiscal 2027 revenue stood at $124.4 million with GAAP operating income of $10.2 million, up from $3.6 million in the prior-year period.
• Annual Recurring Revenue (ARR) reached $501.4 million with 15,506 total paid customers and a dollar-based net retention rate of 98%.
• Announced a corporate restructuring plan in August 2026 reducing headcount by ~15%, with expected restructuring charges between $5.5 million and $7.5 million.

See It, Approve It, Revoke It: Scoped OAuth for Public Apps

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about...