<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <author>
    <name>WeiLai</name>
  </author>
  <generator uri="https://hexo.io/">Hexo</generator>
  <id>https://blog.wetalk.eu.org/</id>
  <link href="https://blog.wetalk.eu.org/" rel="alternate"/>
  <link href="https://blog.wetalk.eu.org/atom.xml" rel="self"/>
  <rights>All rights reserved 2026, WeiLai</rights>
  <subtitle>Stay Hungry,Stay Foolish</subtitle>
  <title>Get busy living</title>
  <updated>2026-08-20T06:20:00.000Z</updated>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="SRE" scheme="https://blog.wetalk.eu.org/tags/SRE/"/>
    <category term="安全" scheme="https://blog.wetalk.eu.org/tags/security/"/>
    <category term="AI Agent" scheme="https://blog.wetalk.eu.org/tags/AI-Agent/"/>
    <category term="提示注入" scheme="https://blog.wetalk.eu.org/tags/%E6%8F%90%E7%A4%BA%E6%B3%A8%E5%85%A5/"/>
    <id>https://blog.wetalk.eu.org/ops/services/agent-instruction-boundary/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/agent-instruction-boundary/"/>
    <published>2026-08-20T06:20:00.000Z</published>
    <summary>一个自治调查 Agent 的工作目录，恰好就是它自己那份常驻指令所在的目录。这是一次性提示注入和永久提示注入的分界线；记录两道失效方式不同的防线、为什么只读挂载解决不了，以及 runbook 自动沉淀该用哪种写入语义。</summary>
    <title>让 Agent 自己长经验，又不让它改自己的指令</title>
    <updated>2026-08-20T06:20:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="ops" scheme="https://blog.wetalk.eu.org/categories/ops/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="SRE" scheme="https://blog.wetalk.eu.org/tags/SRE/"/>
    <category term="可靠性" scheme="https://blog.wetalk.eu.org/tags/%E5%8F%AF%E9%9D%A0%E6%80%A7/"/>
    <category term="静默失败" scheme="https://blog.wetalk.eu.org/tags/%E9%9D%99%E9%BB%98%E5%A4%B1%E8%B4%A5/"/>
    <id>https://blog.wetalk.eu.org/ops/sent-marker-that-lied/</id>
    <link href="https://blog.wetalk.eu.org/ops/sent-marker-that-lied/"/>
    <published>2026-08-18T15:30:00.000Z</published>
    <summary>周报和月报消失了几个星期，没有任何告警、任何错误日志、任何异常指标——因为发送失败也会盖上「已发送」的标记，补发机制看到标记就此收手，完成日志打着 INFO。解剖这次静默丢失的三个共谋，和「标记必须是事实断言」的修复。</summary>
    <title>「已发送」标记撒了几周的谎：一次静默数据丢失的解剖</title>
    <updated>2026-08-18T15:30:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="ops" scheme="https://blog.wetalk.eu.org/categories/ops/"/>
    <category term="工程实践" scheme="https://blog.wetalk.eu.org/tags/%E5%B7%A5%E7%A8%8B%E5%AE%9E%E8%B7%B5/"/>
    <category term="决策记录" scheme="https://blog.wetalk.eu.org/tags/%E5%86%B3%E7%AD%96%E8%AE%B0%E5%BD%95/"/>
    <category term="ADR" scheme="https://blog.wetalk.eu.org/tags/ADR/"/>
    <category term="文档" scheme="https://blog.wetalk.eu.org/tags/%E6%96%87%E6%A1%A3/"/>
    <id>https://blog.wetalk.eu.org/ops/rejected-notes-bucket/</id>
    <link href="https://blog.wetalk.eu.org/ops/rejected-notes-bucket/"/>
    <published>2026-08-18T15:00:00.000Z</published>
    <summary>commit log 记得住每一个做了的决定，却永远不记得那些评估过然后放弃的。在仓库里给决策建档、专门给「被拒绝的方案」留一个桶、并给每次拒绝写上过期条件——这是我用过的性价比最高的工程实践。</summary>
    <title>决策档案里最值钱的是 rejected 桶</title>
    <updated>2026-08-18T15:00:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="SRE" scheme="https://blog.wetalk.eu.org/tags/SRE/"/>
    <category term="安全" scheme="https://blog.wetalk.eu.org/tags/security/"/>
    <category term="AI Agent" scheme="https://blog.wetalk.eu.org/tags/AI-Agent/"/>
    <category term="MCP" scheme="https://blog.wetalk.eu.org/tags/MCP/"/>
    <category term="AIOps" scheme="https://blog.wetalk.eu.org/tags/AIOps/"/>
    <id>https://blog.wetalk.eu.org/ops/services/read-only-by-construction/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/read-only-by-construction/"/>
    <published>2026-08-18T14:30:00.000Z</published>
    <summary>让一个自治 AI Agent 调查生产故障，安全边界不能写在提示词里。四层构造性只读：工具调用否决钩子、只读 MCP 面、不可信输入围栏、双闸修复——每一层都假设上一层会被骗过。</summary>
    <title>只读是构造出来的，不是许诺出来的：让 AI Agent 碰生产的安全设计</title>
    <updated>2026-08-18T14:30:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="SRE" scheme="https://blog.wetalk.eu.org/tags/SRE/"/>
    <category term="AIOps" scheme="https://blog.wetalk.eu.org/tags/AIOps/"/>
    <category term="告警" scheme="https://blog.wetalk.eu.org/tags/alerting/"/>
    <category term="影子灰度" scheme="https://blog.wetalk.eu.org/tags/%E5%BD%B1%E5%AD%90%E7%81%B0%E5%BA%A6/"/>
    <id>https://blog.wetalk.eu.org/ops/services/shadow-run-two-alert-systems/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/shadow-run-two-alert-systems/"/>
    <published>2026-08-18T14:00:00.000Z</published>
    <summary>把第二套告警判定系统以「只记账、不通知」的影子模式接上生产流量：88.6% 的判定一致率、一个藏在三层正当设计背后的恢复标记 bug、一条两边都没错的边界案例，以及为什么影子灰度真正的产品是分歧行。</summary>
    <title>让两个告警系统在真实流量上对赌：影子灰度跑出的第一批数据</title>
    <updated>2026-08-18T14:00:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="Python" scheme="https://blog.wetalk.eu.org/tags/Python/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="SRE" scheme="https://blog.wetalk.eu.org/tags/SRE/"/>
    <category term="MCP" scheme="https://blog.wetalk.eu.org/tags/MCP/"/>
    <category term="AIOps" scheme="https://blog.wetalk.eu.org/tags/AIOps/"/>
    <category term="告警" scheme="https://blog.wetalk.eu.org/tags/alerting/"/>
    <id>https://blog.wetalk.eu.org/ops/services/webhookwise-gatekeeper/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/webhookwise-gatekeeper/"/>
    <published>2026-08-17T11:05:00.000Z</published>
    <summary>一个自部署的告警网关：站在监控系统和通知群之间，把「收到告警」和「打扰人类」拆开。AI 分诊、八道抑制闸门、可追溯的决策链、事务性 Outbox 投递，以及给 AI Agent 的只读 MCP 接口。</summary>
    <title>WebhookWise：我给告警群做了一个「守门人」</title>
    <updated>2026-08-17T11:05:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="ops" scheme="https://blog.wetalk.eu.org/categories/ops/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="Docker" scheme="https://blog.wetalk.eu.org/tags/Docker/"/>
    <category term="buildx" scheme="https://blog.wetalk.eu.org/tags/buildx/"/>
    <category term="QEMU" scheme="https://blog.wetalk.eu.org/tags/QEMU/"/>
    <category term="多架构" scheme="https://blog.wetalk.eu.org/tags/%E5%A4%9A%E6%9E%B6%E6%9E%84/"/>
    <category term="容器" scheme="https://blog.wetalk.eu.org/tags/%E5%AE%B9%E5%99%A8/"/>
    <id>https://blog.wetalk.eu.org/ops/multi-arch-container-image/</id>
    <link href="https://blog.wetalk.eu.org/ops/multi-arch-container-image/"/>
    <published>2026-08-06T12:30:00.000Z</published>
    <summary>用 buildx 和 QEMU 构建跨架构镜像的完整流程，包括 docker-container driver、manifest list 为什么只能在 registry 生成、如何真正验证异构镜像；以及 PEP 668、登录 shell 丢 PATH、多进程容器半死不活、bind mount 下 git 静默失败这四个坑。</summary>
    <title>一个镜像跑遍 amd64 和 arm64：buildx / QEMU，以及四个只在容器里犯的错</title>
    <updated>2026-08-06T12:30:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="ops" scheme="https://blog.wetalk.eu.org/categories/ops/"/>
    <category term="Docker" scheme="https://blog.wetalk.eu.org/tags/Docker/"/>
    <category term="OrbStack" scheme="https://blog.wetalk.eu.org/tags/OrbStack/"/>
    <category term="macOS" scheme="https://blog.wetalk.eu.org/tags/macOS/"/>
    <category term="故障排查" scheme="https://blog.wetalk.eu.org/tags/troubleshooting/"/>
    <id>https://blog.wetalk.eu.org/orbstack-apfs-fix/</id>
    <link href="https://blog.wetalk.eu.org/orbstack-apfs-fix/"/>
    <published>2026-07-23T02:50:00.000Z</published>
    <summary>解决 OrbStack 数据映像位于 HFS+ 时报磁盘空间不足、启动失败的问题，提供迁移数据目录到 APFS 的完整修复与验证流程。</summary>
    <title>OrbStack 启动失败 APFS 修复操作手册</title>
    <updated>2026-07-23T02:50:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="AWS" scheme="https://blog.wetalk.eu.org/categories/AWS/"/>
    <category term="AWS" scheme="https://blog.wetalk.eu.org/tags/AWS/"/>
    <category term="云计算" scheme="https://blog.wetalk.eu.org/tags/cloud-computing/"/>
    <category term="架构设计" scheme="https://blog.wetalk.eu.org/tags/architecture-design/"/>
    <id>https://blog.wetalk.eu.org/aws-services-guide/</id>
    <link href="https://blog.wetalk.eu.org/aws-services-guide/"/>
    <published>2026-07-23T02:20:00.000Z</published>
    <summary>AWS 服务学习笔记，详解计算、存储、数据库、网络、安全与 AI 等核心服务，并附全服务速览、学习路线、典型架构与避坑清单。</summary>
    <title>AWS 服务学习笔记与架构指南</title>
    <updated>2026-07-23T02:20:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="Python" scheme="https://blog.wetalk.eu.org/tags/Python/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <category term="AIOps" scheme="https://blog.wetalk.eu.org/tags/AIOps/"/>
    <category term="告警" scheme="https://blog.wetalk.eu.org/tags/alerting/"/>
    <category term="架构" scheme="https://blog.wetalk.eu.org/tags/architecture/"/>
    <id>https://blog.wetalk.eu.org/ops/services/webhookwise-merged/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/webhookwise-merged/"/>
    <published>2026-07-02T02:00:00.000Z</published>
    <summary>介绍告警中枢 WebhookWise 的架构与设计取舍，含接收入队、AI 与规则双轨分析、去重降噪、事务 Outbox 与全链路可观测。</summary>
    <title>WebhookWise：从小型 AIOps 控制面到全链路可观测性</title>
    <updated>2026-07-02T02:00:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <category term="监控" scheme="https://blog.wetalk.eu.org/tags/monitoring/"/>
    <category term="Shell" scheme="https://blog.wetalk.eu.org/tags/Shell/"/>
    <category term="GitHub Actions" scheme="https://blog.wetalk.eu.org/tags/GitHub-Actions/"/>
    <category term="飞书" scheme="https://blog.wetalk.eu.org/tags/feishu/"/>
    <category term="踩坑" scheme="https://blog.wetalk.eu.org/tags/pitfalls/"/>
    <id>https://blog.wetalk.eu.org/ops/services/monitoring-merged/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/monitoring-merged/"/>
    <published>2026-06-22T23:30:44.000Z</published>
    <summary>记录监控告警从单机脚本逐步演进到多机、反向心跳兜底、监控 GitHub Runner，最终统一接入 Uptime Kuma 的过程。</summary>
    <title>从手搓多机监控到统一接入 Uptime Kuma</title>
    <updated>2026-06-22T23:30:44.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="featured" scheme="https://blog.wetalk.eu.org/tags/featured/"/>
    <category term="可观测性" scheme="https://blog.wetalk.eu.org/tags/observability/"/>
    <category term="Kubernetes" scheme="https://blog.wetalk.eu.org/tags/Kubernetes/"/>
    <category term="eBPF" scheme="https://blog.wetalk.eu.org/tags/eBPF/"/>
    <category term="Pixie" scheme="https://blog.wetalk.eu.org/tags/Pixie/"/>
    <category term="ARM64" scheme="https://blog.wetalk.eu.org/tags/ARM64/"/>
    <id>https://blog.wetalk.eu.org/ops/services/pixie-arm-kernel6.17/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/pixie-arm-kernel6.17/"/>
    <published>2026-06-16T04:30:00.000Z</published>
    <summary>记录在 ARM64 与内核 6.17 环境部署 Pixie 的完整过程，结论是其 eBPF 探针全部加载失败不可用，并给出替代方案。</summary>
    <title>在 ARM64 + 新内核(6.17) 上踩 Pixie 的坑：从满怀期待到果断放弃</title>
    <updated>2026-06-16T04:30:00.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/hermes-install-setup/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/hermes-install-setup/"/>
    <published>2026-04-15T03:05:31.000Z</published>
    <summary>记录 Nous Research 开源 AI 代理 Hermes Agent 的安装与初始化，涵盖核心特性、环境要求与部署步骤。</summary>
    <title>hermes 安装与初始化记录</title>
    <updated>2026-04-15T03:05:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/openclaw-install-setup/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/openclaw-install-setup/"/>
    <published>2026-03-30T03:05:31.000Z</published>
    <summary>记录在 ARM64 环境下安装 OpenClaw、配置 Gateway 模式与系统服务、成本预算控制及设备批准等初始化过程。</summary>
    <title>OpenClaw 安装与初始化记录</title>
    <updated>2026-03-30T03:05:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="Kubernetes" scheme="https://blog.wetalk.eu.org/categories/Kubernetes/"/>
    <category term="Kubernetes" scheme="https://blog.wetalk.eu.org/tags/Kubernetes/"/>
    <id>https://blog.wetalk.eu.org/ops/k8s/kuberay-usage/</id>
    <link href="https://blog.wetalk.eu.org/ops/k8s/kuberay-usage/"/>
    <published>2025-05-11T15:43:31.000Z</published>
    <summary>介绍 Ray 分布式框架与 KubeRay，演示在 Kubernetes 上安装 Operator、部署 RayCluster 与提交任务。</summary>
    <title>kuberay简单使用</title>
    <updated>2025-05-11T15:43:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="Kubernetes" scheme="https://blog.wetalk.eu.org/categories/Kubernetes/"/>
    <category term="Kubernetes" scheme="https://blog.wetalk.eu.org/tags/Kubernetes/"/>
    <id>https://blog.wetalk.eu.org/ops/k8s/multi-version-traffic-routing/</id>
    <link href="https://blog.wetalk.eu.org/ops/k8s/multi-version-traffic-routing/"/>
    <published>2025-05-04T14:43:31.000Z</published>
    <summary>讲解 Kubernetes 多版本流量区分，演示基于请求头路由，并用 Traefik 与 Istio 实现灰度发布。</summary>
    <title>多个版本流量区分</title>
    <updated>2025-05-04T14:43:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/ssl-cert-tools/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/ssl-cert-tools/"/>
    <published>2025-01-20T03:05:31.000Z</published>
    <summary>介绍使用 Certimate 与 dnsmgr 工具，通过 docker-compose 部署并配置工作流实现 SSL 证书的自动申请与管理。</summary>
    <title>cert工具使用</title>
    <updated>2025-01-20T03:05:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/infisical/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/infisical/"/>
    <published>2024-11-30T03:05:31.000Z</published>
    <summary>介绍开源密钥管理平台 Infisical 的用途，演示 Helm 自建、服务端验证、K8s Operator 客户端接入及限制修改。</summary>
    <title>infisical 基础使用</title>
    <updated>2024-11-30T03:05:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/nightngale/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/nightngale/"/>
    <published>2024-11-25T10:05:31.000Z</published>
    <summary>介绍开源云原生监控夜莺（Nightingale）的用途，演示其部署、Categraf 采集器接入与验证。</summary>
    <title>nightngale使用</title>
    <updated>2024-11-25T10:05:31.000Z</updated>
  </entry>
  <entry>
    <author>
      <name>WeiLai</name>
    </author>
    <category term="services" scheme="https://blog.wetalk.eu.org/categories/services/"/>
    <category term="运维" scheme="https://blog.wetalk.eu.org/tags/ops/"/>
    <id>https://blog.wetalk.eu.org/ops/services/k6/</id>
    <link href="https://blog.wetalk.eu.org/ops/services/k6/"/>
    <published>2024-11-25T03:05:33.000Z</published>
    <summary>介绍 k6 的负载、基准等测试用途，演示用 xk6 构建定制版并将结果输出到 InfluxDB 进行压测。</summary>
    <title>k6安装测试</title>
    <updated>2024-11-25T03:05:33.000Z</updated>
  </entry>
</feed>
