# health checks Health checks are periodic assessments that verify the status, availability, or performance of services and nodes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Incident Report: July 22, 2026 DevFeed: [Incident Report: July 22, 2026]() Original publisher: [Read original article]() Author: Karina Devadoss Published: 2026-08-14T17:06:07Z Content type: news Language: en Sources: [HubSpot]() Topics: [incident](), [configuration](), [bug](), [health checks](), [client]() Tags: [2026](), [bug](), [change](), [configuration](), [customers](), [engineering](), [errors](), [europe](), [health-checks](), [hubspot](), [incident](), [memory](), [network](), [performance](), [report](), [services]() ### AI overview HubSpot reports that a configuration change triggered a latent defect in a core CRM service, causing European customers to experience CRM access disruptions for approximately 55 minutes on July 22, 2026. No data was lost, and non-European regions operated without interruption. ### Source excerpt Customers in Europe faced CRM access issues on July 22 due to a configuration change. Learn about the incident, its impact, and our commitment to improved reliability. ## GraphOS MCP Server Connects AI Agents to Graph Health Checks DevFeed: [GraphOS MCP Server Connects AI Agents to Graph Health Checks]() Original publisher: [Read original article]() Author: Dale Seo Published: 2026-07-21T12:03:01Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [MCP Server](), [Artificial Intelligence](), [health checks]() Tags: [ai](), [ai-agents](), [announcement](), [graphos](), [health-checks](), [mcp-server](), [metrics]() ### AI overview Apollo announces GraphOS MCP Server, a hosted MCP server that connects AI agents to GraphOS. Agents can access graph health information including launch status, lint results, router configuration, and traffic metrics. ### Source excerpt GraphOS MCP Server connects AI agents to GraphOS, so agents can run graph health checks: launch status, lint results, router config, and traffic metrics. ## Top System Design Performance Metrics DevFeed: [Top System Design Performance Metrics]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-07-14T08:36:41Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [benchmarking](), [Availability](), [Architecture & Design](), [Scalability](), [Load Balancing](), [health checks](), [Concurrency](), [Disaster Recovery](), [Database](), [sharding](), [IO](), [API]() Tags: [api](), [availability](), [blocking](), [concurrency](), [database](), [disaster-recovery](), [health-checks](), [load-balancing](), [performance](), [performance-metrics](), [scalability](), [sharding](), [system-design]() ### AI overview A tutorial on system design performance metrics, focusing on availability and throughput. It explains how these metrics are measured and outlines techniques such as load balancing, health checks, failover, redundancy, disaster recovery, query optimization, sharding, and asynchronous processing. ### Source excerpt Must Know Metrics ## Linux Server Health Checks: 10 Metrics Every Sysadmin Should Monitor DevFeed: [Linux Server Health Checks: 10 Metrics Every Sysadmin Should Monitor]() Original publisher: [Read original article]() Author: Sujitha Paduchuri, ManageEngine Published: 2026-07-06T12:13:41Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Monitoring](), [Linux performance](), [health checks]() Tags: [blog](), [cpu](), [disk-space](), [guests](), [health-checks](), [linux](), [linux-performance](), [load](), [memory](), [metrics](), [monitoring](), [observability](), [performance](), [performance-monitoring](), [server](), [sysadmins]() ### AI overview A practical guide to monitoring Linux server health through metrics that can reveal resource problems earlier than broad CPU, memory, or disk-usage figures. It discusses iowait, load average, active swap activity, and inode exhaustion, along with warning signs and follow-up investigations. ### Source excerpt Servers give you warnings before they fail. Most sysadmins performing Linux server monitoring miss them because they're watching the wrong numbers. The metrics that actually matter are one level deeper: iowait instead of CPU percentage, active swap paging instead of memory usage, inode counts instead of just disk space. Continue reading... ## pproxy: a forward proxy that load-balances a pool of upstream proxies DevFeed: [pproxy: a forward proxy that load-balances a pool of upstream proxies]() Original publisher: [Read original article]() Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [Andika Ahmad Ramadhan -- Blog]() Topics: [proxy](), [client](), [health checks](), [HTTP]() Tags: [client](), [health](), [health-checks](), [http](), [prometheus](), [proxy](), [reload](), [round-robin](), [socks5](), [tls]() ### AI overview This article presents pproxy, a forward proxy that distributes client traffic across upstream proxies. It describes active health checks, round-robin selection, failover within requests, hot configuration reloads, per-user authentication, and Prometheus metrics. ### Source excerpt pproxy is a forward proxy that load-balances client traffic across a pool of upstream proxies with active health checks and hot config reload, so switching proxy providers means editing one config file instead of every client. ## Deploying Temporal Workers to Amazon ECS DevFeed: [Deploying Temporal Workers to Amazon ECS]() Original publisher: [Read original article]() Author: Ebenezer Ankrah Published: 2026-04-02T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Amazon Elastic Container Service](), [Deployment](), [AWS IAM](), [Dockerfile](), [container](), [health checks](), [Amazon Web Services]() Tags: [amazon](), [deployment](), [docker](), [docker-image](), [ecs](), [environment-variables](), [health-checks](), [how-to](), [iam]() ### AI overview A guide to deploying Temporal Workers on Amazon ECS with Fargate. It explains container configuration, health checks, graceful shutdown, task definitions, IAM roles, secret injection through SSM Parameter Store, and outbound connectivity requirements. ### Source excerpt A comprehensive guide to deploying Temporal Workers on Amazon ECS with Fargate. Covers container config, IAM roles, scaling, and cost-saving with Fargate Spot. ## From Bash to Bliss: Scaling Vespa Operations with Temporal DevFeed: [From Bash to Bliss: Scaling Vespa Operations with Temporal]() Original publisher: [Read original article]() Author: Martynas Jakimčikas Published: 2026-01-21T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Platform Engineering](), [Orchestration](), [Scripting, bash](), [Automation](), [health checks](), [upgrade]() Tags: [automation](), [commands](), [complexity](), [health-checks](), [maintenance](), [orchestration](), [platform](), [scheduled](), [script](), [self-service](), [upgrade]() ### AI overview This article describes how Vinted's platform team handled growing maintenance demands for its Vespa search infrastructure. As the environment expanded from hundreds to more than a thousand nodes and included many deployments, Bash scripts and Knife commands became difficult to manage. The team moved toward durable orchestration with Temporal, automated health checks, scheduled upgrades, and self-service guardrails. ### Source excerpt Growing platform - Growing maintenance Keeping the Lights On (KTLO) is an essential, yet often taxing, part of a platform engineer's role. It represents the routine operational work required to keep the business running and the platform stable. For our team, this primarily involves maintenance on our search engine, Vespa - ranging from version upgrades and service restarts to draining traffic from nodes for hardware replacements. ## 20 years of Getting Things Done DevFeed: [20 years of Getting Things Done]() Original publisher: [Read original article]() Author: Tom Published: 2025-11-27T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [systems](), [DevOps](), [Monitoring](), [backups](), [health checks](), [Disaster Recovery]() Tags: [2](), [advice](), [backup](), [best-practices](), [devops](), [getting-things-done](), [gtd](), [leadership](), [learnings](), [linux](), [monitoring](), [productivity](), [recovery](), [time-management](), [workshop]() ### AI overview A reflection on 20 years of using Getting Things Done, including how external systems shaped the author's work as a system administrator and DevOps engineer. It describes replacing manual backup checks with failure notifications and introducing monitoring and health checks to move operations from reactive to proactive. ### Source excerpt Reflections and practical tips from 20 years using Getting Things Done, plus a short workshop plan for leaders who want actionable routines. ## How to choose a business VPN DevFeed: [How to choose a business VPN]() Original publisher: [Read original article]() Published: 2025-09-23T17:52:03Z Content type: tutorial Language: en Sources: [Learn on Tailscale]() Topics: [Virtual Private Network](), [tailscale](), [networking](), [Encryption](), [MFA](), [Single sign-on (SSO)](), [Logging](), [health checks](), [remote access]() Tags: [authentication](), [encryption](), [health-checks](), [how-to](), [logging](), [mfa](), [networking](), [remote-access](), [vpn]() ### AI overview This guide explains how to evaluate a business VPN, covering remote-access and site-to-site models, protocol support, identity integration, logging, encryption, SSO, MFA, device posture checks, and least-privilege policies. It presents Tailscale's peer-to-peer, identity-based approach as a way to avoid VPN backhaul bottlenecks and overly broad network access. ### Source excerpt Learn how to choose a business VPN that actually works for real teams. Cut through the noise and find secure, simple solutions that won't create headaches six months later. ## Temporal v0.28.0 changelog DevFeed: [Temporal v0.28.0 changelog]() Original publisher: [Read original article]() Author: Cully Wakelin Published: 2020-07-31T04:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [changelog](), [version](), [API](), [gRPC](), [TLS (Transport Layer Security)](), [Helm charts](), [Kubernetes](), [retry](), [Command-line interface](), [health checks](), [Go]() Tags: [changelog](), [cli](), [grpc](), [health-checks](), [helm-charts](), [kubernetes](), [product-news](), [release](), [retries](), [tls](), [version]() ### AI overview Temporal v0.28.0 is a release changelog covering changes since the project forked from Cadence. It describes the move from Thrift/TChannel to Protobuf/gRPC, TLS-encrypted communication, standardized errors and health checks, Kubernetes Helm deployment, workflow and activity retry and timeout refactors, and new CLI administration commands. ### Source excerpt Today is an exciting day for us! Temporal is releasing its newest version, v0.28.0, bringing us one step closer to a stable production ready release. ## What's Coming To Keycloak DevFeed: [What's Coming To Keycloak]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2019-09-03T00:00:00Z Content type: opinion Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [account](), [React](), [WebAuthn](), [Kubernetes](), [Operator Lifecycle Manager](), [API](), [Encryption](), [LDAP](), [health checks](), [Testing]() Tags: [account](), [api](), [authentication](), [automated](), [console](), [encryption](), [health-checks](), [idm](), [kerberos](), [keycloak](), [kubernetes](), [kubernetes-secrets](), [ldap](), [openid-connect](), [operator](), [password](), [rest-api](), [saml](), [software](), [sso](), [usability](), [user-experience](), [vault]() ### AI overview Keycloak's 2019 roadmap outlines planned work on a new React-based account console, WebAuthn authentication, a Kubernetes operator, external vault integration, user profiles, metrics and health checks, and improved automated testing and builds. ### Source excerpt New Account Console and Account REST API The current account console is getting dated. It is also having issues around usability and being hard to extend. For this reason we had the UXD team at Red Hat develop wireframes for a new account console. The new console is being implemented with React.js providing a better user experience as well as making it easier to extend and customise. JIRA - Account Console JIRA - Account REST API WebAuthn We are working towards adding WebAuthn support both for two factor authentication and passwordless experience. This task is not as simple as adding an authenticator for WebAuth, but will also require work on improving authentication flows and the account console. Design proposal - Authentication flow improvements Design proposal - WebAuthn Authenticator Design proposal - WebAuthn Two factor JIRA - Two factor JIRA - Passwordless Operator Operators are becoming an important way to manage software running on Kubernetes and we are working on an operator for Keycloak. The aim is to have an operator published on OperatorHub.io soon which provides basic install and seamless upgrade capabilities. This will be based on the awesome work done by the Red Hat Integreatly team. JIRA Integreatly Keycloak Operator Vault At the moment to keep credentials such as LDAP bind credentials more secure it is required to encrypt the whole database. This can be complex and can also have a performance overhead. We are working towards enabling loading credentials, such as LDAP bind credential and SMTP password, from an external vault. We're providing a built-in integration with Kubernetes secrets as well as an SPI allowing integrating with any vault provider. In the future we will also provide the option to encrypt other more dynamic credentials at rest in the database. JIRA - Vault JIRA - Encryption at rest User Profile Currently there's no single place to define user profiles for a realm. To resolve this we are planning to introduce the Profile SPI, which w ## Stack Overflow: How We Do Monitoring - 2018 Edition DevFeed: [Stack Overflow: How We Do Monitoring - 2018 Edition]() Original publisher: [Read original article]() Published: 2018-11-29T00:00:00Z Content type: article Language: en Sources: [Nick Craver]() Topics: [Monitoring](), [Stack Overflow](), [Automation](), [data](), [telemetry](), [Architecture & Design](), [health checks]() Tags: [architecture](), [automation](), [blog](), [data](), [health-checks](), [logs](), [metrics](), [monitoring](), [telemetry]() ### AI overview This article explains how Stack Overflow approaches application monitoring. It discusses monitoring concepts, automation and alert thresholds, trade-offs in operational decisions, and data types including logs, metrics, and health checks. ### Source excerpt This is #4 in a very long series of posts on Stack Overflow's architecture. Previous post (#3): Stack Overflow: How We Do Deployment - 2016 Edition What is monitoring? As far as I can tell, it means different things to different people. But we more or less agree on the concept. I think. Maybe. Let's find out! When someone says monitoring, I think of: ...but evidently some people think of other things. Those people are obviously wrong, but let's continue. When I'm not a walking zombie after reading a 10,000 word blog post some idiot wrote, I see monitoring as the process of keeping an eye on your stuff, like a security guard sitting at a desk full of cameras somewhere. Sometimes they fall asleep-that's monitoring going down. Sometimes they're distracted with a doughnut delivery-that's an upgrade outage. Sometimes the camera is on a loop-I don't know where I was going with that one, but someone's probably robbing you. And then you have the fire alarm. You don't need a human to trigger that. The same applies when a door gets opened, maybe that's wired to a siren. Or maybe it's not. Or maybe the siren broke in 1984. I know what you're thinking: Nick, what the hell? My point is only that monitoring any application isn't that much different from monitoring anything else. Some things you can automate. Some things you can't. Some things have thresholds for which alarms are valid. Sometimes you'll get those thresholds wrong (especially on holidays). And sometimes, when setting up further automation isn't quite worth it, you just make using human eyes easier. What I'll discuss here is what we do. It's not the same for everyone. What's important and "worth it" will be different for almost everyone. As with everything else in life, it's full of trade-off decisions. Below are the ones we've made so far. They're not perfect. They are evolving. And when new data or priorities arise, we will change earlier decisions when it warrants doing so. That's how brains are supposed to work. A