Fortinet vs Grafana Labs

Cybersecurity stock Zscaler's charts turn bullish: Jay Woods

In a CNBC Pro segment, technician Jay Woods discusses Zscaler (ZS), a cybersecurity company that has underperformed its sector peers. While CrowdStrike, Fortinet, Okta, and Palo Alto Networks have gained over 100% year-to-date, Zscaler shares fell as much as 65% from 52-week highs and remain down 13% this year. However, Woods observes a bottoming formation on both daily and weekly charts, with a bullish crossover in MACD and a breakout above $195 resistance. He suggests upside targets of $250-$265, representing 25-30% potential upside, with support at $165. The analysis highlights relative rotation within the cybersecurity sector, indicating that laggards like Zscaler may see renewed strength.

• Zscaler (ZS) shares fell as much as 65% from 52-week highs and remain down 13% year-to-date.
• CrowdStrike, Fortinet, Okta, and Palo Alto Networks have each gained over 100% year-to-date.
• Jay Woods identifies a bullish double bottom formation on Zscaler's weekly chart.

Fortinet Expands U.S. Presence with New Company-Owned Innovation Hub in New York City

Fortinet announced the opening of a new company-owned innovation hub in New York City, expanding its U.S. presence. This is part of Fortinet's strategic growth and investment in innovation.

Stanford Athletics And Cybersecurity Leader Fortinet Team Up For Multi-Year Sponsorship

Fortinet announced a multi-year sponsorship with Stanford Athletics (Aug 28, 2026). Also new: Fortinet Federal Achieves CMMC Level 2 Certification (Aug 26, 2026).

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.