# Logging Published articles for Logging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building an Internal Developer Platform with Artificial Intelligence DevFeed: [Building an Internal Developer Platform with Artificial Intelligence]() Original publisher: [Read original article]() Author: Ben Linders Published: 2026-09-17T11:11:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [internal developer platform](), [AI Development](), [AI search](), [agent observability](), [OpenTelemetry](), [telemetry]() Tags: [agent](), [agents](), [artificial-intelligence](), [culture-methods](), [developer-experience](), [developer-platform](), [distributed-tracing](), [guardrails](), [internal-developer-platform](), [logging](), [logs](), [metrics](), [news](), [opentelemetry](), [platform-artificial-intelligence](), [platform-engineering](), [prometheus](), [traces]() ### AI overview This news article covers a KubeCon presentation about using AI agents as an internal developer platform. It discusses semantic search across sources such as Git, Slack, Jira, repositories, pull requests, and wiki pages; guardrails for controlling actions; and logs, metrics, and traces for understanding agent behavior. The speakers also describe OpenTelemetry conventions for GenAI and related observability tools. ### Source excerpt Agents are becoming the new developer platform, using semantic search with data from tools like Git, Slack, and Jira for context. Things to consider are setting guardrails to block or allow things, and using logs, metrics, and traces to understand agent behavior. By Ben Linders ## Profiling App Engine Memcached DevFeed: [Profiling App Engine Memcached]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-01T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Latency](), [Logging](), [Data structures]() Tags: [engineering](), [infrastructure](), [latency](), [logging](), [memcached](), [news](), [patterns](), [profiling](), [tests]() ### AI overview Khan Academy engineers profile App Engine Memcached to estimate access latency and evaluate whether on-demand content fetching could support separate content trees for each language. Most requests showed 1-4 ms latency, usually below 10 ms, while a single multi-get performed similarly to a single get. ### Source excerpt By Ben Kraft Last year, Willow wrote about how we optimized our in-memory content data to take up ... Read more ## A Threat Hunter's Guide to Detecting Malicious Activity in GitHub Audit Logs DevFeed: [A Threat Hunter's Guide to Detecting Malicious Activity in GitHub Audit Logs]() Original publisher: [Read original article]() Author: Julie Agnes Sparks, Juvenal Araujo Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Datadog Security Labs]() Topics: [GitHub](), [Threat Hunting & Intel](), [Security](), [Logging](), [Authentication](), [personal access token]() Tags: [authentication](), [github](), [logging](), [oauth](), [personal-access-token](), [secrets](), [security](), [security-research]() ### AI overview This article examines threats targeting GitHub organizations, including compromised accounts, personal access tokens, OAuth tokens, leaked secrets, phishing, and malicious extensions or OAuth apps. It describes GitHub audit-log queries and behaviors that can help detect account compromise, reconnaissance, and source-code exfiltration. ### Source excerpt In this post, we walk through different threats to GitHub and how to detect them. ## CISA's Logging Reference Architecture for OMB M-26-14: What federal agencies should do next DevFeed: [CISA's Logging Reference Architecture for OMB M-26-14: What federal agencies should do next]() Original publisher: [Read original article]() Author: Woody Walton Published: 2026-09-16T00:00:00Z Content type: article Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [cisa](), [Logging](), [cybersecurity and infrastructure security agency](), [log management](), [Architecture & Design](), [implementation](), [audit](), [Security]() Tags: [architecture](), [audit](), [cisa](), [cybersecurity-and-infrastructure-security-agency](), [cybersecurity-open-source-standards-log-management-government](), [government](), [implementation](), [logging](), [logs](), [public-sector](), [security]() ### AI overview This Elastic blog explains CISA's Logging Reference Architecture for OMB M-26-14 and the actions federal civilian executive branch agencies must take. It highlights planning and maturity deadlines, recommends assessing existing capabilities and documenting gaps, and discusses storage tiers, retrieval, immutability, and audit requirements. ### Source excerpt Now that CISA has released its Logging Reference Architecture (LRA) for OMB M-26-14, federal agencies tasked to complete their logging plans. In this blog, we walk you through the most important aspects of the LRA guidance. ## Atlassian Automates Root Cause Analysis by Correlating Metrics, Logs and Traces DevFeed: [Atlassian Automates Root Cause Analysis by Correlating Metrics, Logs and Traces]() Original publisher: [Read original article]() Author: Craig Risi Published: 2026-09-15T12:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [incident](), [atlassian](), [telemetry](), [SIEM, Security, Observability](), [tracing](), [Cloud Native Ecosystem](), [OpenTelemetry]() Tags: [atlassian](), [atlassian-automated-rca](), [cloud-native](), [defects](), [devops](), [distributed](), [incident](), [incident-response](), [logging](), [logs](), [metrics](), [news](), [opentelemetry](), [root-cause-analysis](), [services](), [telemetry](), [traces](), [tracing]() ### AI overview Atlassian has outlined an approach to automating root cause analysis for large-scale cloud-native incidents. It correlates metrics, logs, distributed traces, and service topology to detect anomalies, align them in time, trace dependencies, and produce ranked hypotheses about likely fault origins and propagation paths. ### Source excerpt Atlassian has outlined a new approach to automating root cause analysis for large-scale cloud-native incidents, using correlation across metrics, logs, distributed traces, and service topology to generate ranked hypotheses about where failures originate and how they propagate. By Craig Risi ## AWS Security Reference Architecture: A deep dive into PCI DSS compliance DevFeed: [AWS Security Reference Architecture: A deep dive into PCI DSS compliance]() Original publisher: [Read original article]() Author: Avik Mukherjee Published: 2026-09-14T17:46:56Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Security](), [Architecture & Design](), [Network Segmentation](), [Encryption](), [Logging](), [Access Control](), [Cloud]() Tags: [access-control](), [amazon-web-services](), [announcements](), [architecture](), [compliance](), [encryption](), [foundational-100](), [logging](), [network-segmentation](), [pci-dss](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS announces the AWS Security Reference Architecture (AWS SRA) PCI DSS Deep Dive, a guide that extends the core AWS SRA with prescriptive architecture-level guidance for organizations handling cardholder data on AWS. It explains how AWS SRA patterns address PCI DSS concerns including account scoping, network segmentation, encryption, logging, and access control. ### Source excerpt Amazon Web Services (AWS) is excited to announce the publication of the AWS Security Reference Architecture (AWS SRA) Payment Card Industry (PCI) Data Security Standard (DSS) Deep Dive. This new guide extends the core AWS SRA to provide prescriptive, architecture-level guidance for organizations that store, process, or transmit cardholder data on AWS. Organizations subject to [...] ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory with PHP DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory with PHP]() Original publisher: [Read original article]() Author: Amanda Lange, Matthew Setter Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Composer](), [Large Language Model](), [context](), [PHP](), [Tutorial](), [Orchestration](), [OpenAI]() Tags: [agent](), [ai](), [api](), [code](), [context](), [conversation-memory](), [developer-insights](), [environment-variables](), [how-to](), [llm](), [logging](), [ngrok](), [orchestration](), [php](), [phpstorm](), [voice-api]() ### AI overview This tutorial shows how to build a PHP service with Open Swoole that uses Twilio Conversation Memory to preserve caller context, preferences, and action history across separate inbound calls. It covers the required accounts, tools, environment variables, Composer setup, OpenAI integration, logging, and Memory Store configuration. ### Source excerpt In this tutorial you'll make a PHP service using Open Swoole that retains caller context, preferences and action history across multiple separate inbound calls. ## Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging DevFeed: [Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging]() Original publisher: [Read original article]() Author: Slava Sarzhan Published: 2026-09-09T16:08:31Z Content type: release Language: en Sources: [Blog - Percona]() Topics: [PostgreSQL](), [Encryption](), [Logging](), [Kubernetes](), [Open Source]() Tags: [cloud](), [encryption](), [hashicorp-vault](), [kubernetes](), [logging](), [open-source](), [operator](), [percona](), [percona-operator-for-postgresql](), [postgresql](), [release](), [replication](), [security](), [slavasarzhan-pg]() ### AI overview Percona Operator for PostgreSQL 3.1.0 adds transparent data encryption with pg_tde, logical replicas for read-only workloads, and persistent logging across Pod restarts. The release also adds official RKE2 support and full ARM64 images. ### Source excerpt Percona Operator for PostgreSQL 3.1.0 takes on three things that decide whether a PostgreSQL platform passes review: is the data encrypted at rest, can it serve reads without straining the primary, and are the logs there when you need them. This release answers all three inside the custom resource, so none of them is a ... Continued The post Percona Operator for PostgreSQL 3.1.0: Transparent Data Encryption, Logical Replicas, and Persistent Logging appeared first on Percona. ## See you at Elastic{ON} 2026 DevFeed: [See you at Elastic{ON} 2026]() Original publisher: [Read original article]() Author: Dan Courcy Published: 2026-09-08T00:00:00Z Content type: news Language: en Sources: [Elastic Blog - Elasticsearch, Kibana, and ELK Stack]() Topics: [AI search](), [telemetry]() Tags: [ai](), [ai-agent](), [developer](), [elasticsearch](), [event](), [logging](), [metrics](), [observability](), [platform-observability-search-security](), [production](), [search](), [sre]() ### AI overview Elastic announces its Elastic{ON} 2026 global event tour, with sessions for developers on scaling AI agents with Elasticsearch and for SREs on observability, logging, metrics, and AI-assisted incident response. ### Source excerpt Elastic{ON} kicks off this September with seven stops in cities around the world. Elastic's CEO Ash Kulkarni will be appearing at stops across the tour, opening keynotes with a candid conversation about why your data has never been more valuable. ## MCP Logging in Spring AI DevFeed: [MCP Logging in Spring AI]() Original publisher: [Read original article]() Author: Burak Gökmen Published: 2026-09-06T23:19:21Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Model Context Protocol](), [log management](), [AI Development](), [Remote Procedure Call (RPC)](), [telemetry]() Tags: [logging](), [mcp](), [mcp-server](), [opentelemetry](), [popular](), [rpc](), [spring](), [spring-ai](), [spring-ai-mcp-popular](), [spring-boot](), [tutorial]() ### AI overview A tutorial on MCP logging in Spring AI, covering server-to-client log notifications, client-controlled severity levels, and migration guidance following the feature's deprecation. ### Source excerpt Learn about MCP logging in Spring AI, both in an MCP server and a client. The post MCP Logging in Spring AI first appeared on Baeldung. ## Quiz: Understanding the Python Traceback DevFeed: [Quiz: Understanding the Python Traceback]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-06T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [Exception](), [log management]() Tags: [examples](), [exception](), [logging](), [python]() ### AI overview An interactive 12-question quiz that tests understanding of Python tracebacks, including how to read them from the bottom up, interpret their parts, recognize common exceptions, and log tracebacks while handling exceptions. ### Source excerpt Check your understanding of Python tracebacks. Practice reading the error message line, recognizing common exceptions, and logging a traceback. ## Rootless Podman: Preserving Source IPs DevFeed: [Rootless Podman: Preserving Source IPs]() Original publisher: [Read original article]() Author: Jan Rodak Published: 2026-09-04T14:25:02Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [Networks](), [Access Control](), [Logging]() Tags: [blog](), [bridge](), [container](), [containers](), [ipv4](), [ipv6](), [logging](), [networks](), [podman](), [port](), [rate-limiting](), [routing](), [tips-and-tricks]() ### AI overview This article explains how Pesto, a companion tool from the passt project, addresses Rootless Podman's inability to preserve incoming client source IPs on bridge networks. Pesto updates pasta's forwarding table so traffic reaches containers without source-address rewriting, while retaining existing port-mapping capabilities. The article also documents configuration steps, traffic flow, supported networking features, and limitations when switching from the current forwarder. ### Source excerpt Rootless Podman has a long-standing limitation reported since 2020: containers on bridge networks can't see the real source IP of incoming connections. The `rootlessport` userspace proxy rewrites the source to the container's own subnet address, breaking IP-based access control, logging, and rate limiting. Pesto, a new companion tool from the passt project solves this. Pesto [...] ## When the action succeeds and the audit write doesn't DevFeed: [When the action succeeds and the audit write doesn't]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Logging](), [systems](), [payload]() Tags: [audit](), [distributed-transaction](), [logging](), [metric](), [retry]() ### AI overview The article examines why audit logs can become unreliable when an application performs an action and writes its audit record as separate operations. It describes silent gaps, phantom events, and duplicate events caused by failures, ordering, and retries, emphasizing that audit records must remain trustworthy evidence. ### Source excerpt When the action succeeds and the log write fails, you get a gap that nothing alerts on. Here is the write path that closes it. ## Astro 7.3 DevFeed: [Astro 7.3]() Original publisher: [Read original article]() Author: Matthew Phillips Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [The Astro Blog]() Topics: [Server](), [log management](), [Caching](), [Command-line interface]() Tags: [astro](), [cache](), [cli](), [cloudflare](), [logging](), [release](), [servers]() ### AI overview Astro 7.3 adds support for multiple preview servers, routes runtime logging to custom image services and cache providers, and introduces a Cloudflare helper for custom worker entrypoints. ### Source excerpt Astro 7.3 adds an --ignore-lock flag for astro preview, passes Astro's runtime logger into custom image services and cache providers, and ships a finalize() helper for Cloudflare custom worker entrypoints. ## 5 Billion Records, 10 Terabytes, Four Weeks: A Real Data Migration Playbook DevFeed: [5 Billion Records, 10 Terabytes, Four Weeks: A Real Data Migration Playbook]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-09-02T07:27:50Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [migration](), [data](), [Databases](), [API](), [Logging](), [Tech Debt]() Tags: [api](), [data](), [database](), [logging](), [migration](), [tech-debt]() ### AI overview This Wix engineering article presents a data migration playbook based on lessons from large and complex migrations. It argues that success depends less on changing tooling than on identifying recurring problems before migration begins, especially by auditing inconsistent source data, implementing a read phase, and logging suspicious fields and structures. It also outlines using a V2 API, an API proxy, population-based rollout, change data capture, continued synchronization, and eventual decommissioning of V1. ### Source excerpt By the time you finish reading this, someone at Wix is probably in the middle of a data migration. We've run migrations that lasted anywhere from a few months to two years. More recently, we've completed large and complex migrations in a few weeks. The difference wasn't the tooling, which barely changed. It was that we had finally learned which problems show up in every migration, and started dealing with them before the migration began instead of in the middle of it. Recap: Why We Migrate,... ## Primer on Python Decorators DevFeed: [Primer on Python Decorators]() Original publisher: [Read original article]() Author: Geir Arne Hjelle Published: 2026-09-01T14:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [Code](), [Caching](), [Authorization](), [log management]() Tags: [caching](), [code](), [logging](), [python](), [tutorial]() ### AI overview A tutorial explaining Python decorators: functions that wrap other functions to alter or extend behavior. It covers writing custom decorators, stacking them, and how decorator order affects results. ### Source excerpt In this tutorial, you'll look at what Python decorators are and how you define and use them. Decorators can make your code more readable and reusable. Come take a look at how decorators work under the hood and practice writing your own decorators. ## What's new in Svelte: September 2026 DevFeed: [What's new in Svelte: September 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-09-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [releases](), [Command-line interface](), [migration](), [Model Context Protocol]() Tags: [add-ons](), [cli](), [logging](), [mcp](), [migration](), [release](), [routing](), [september-2026](), [svelte]() ### AI overview A release update covering Svelte 5.57, the SvelteKit 3 release-candidate line, and sv CLI changes. It highlights new APIs, routing and adapter updates, an AI-tools add-on, and a task-based SvelteKit 3 migration. ### Source excerpt This month, Svelte 5.57 shipped with new SvelteMap methods and a few quality-of-life additions while SvelteKit 3 got closer to the finish line with its Release Candidate. The sv CLI also got a new ai-tools add-on that replaces the old mcp one, and sv@next now ships a task-based sveltekit-3 migration for existing apps. Let's dive a bit deeper! What's new in Svelte SvelteMap now has getOrInsert and getOrInsertComputed methods for the common "read or initialize" pattern (5.57.0, Docs, #18728) createContext now returns a third has function so you can check whether a context has been set without triggering the get error (5.57.0, Docs, #18472)