Latest public discussions in the Ops & support industry on ZIWM. Browse public Q&A, peer discussions, and local professional topics across U.S. industries including USPS, accounting, construction, healthcare, trucking, e-commerce, legal, real estate, restaurants, and technology. Sign in to read full posts, ask questions, and join the conversation.
tech-ops-support
值班最怕一上来就被群里催，CPU、磁盘、网络、应用日志全都红一点。我的习惯是先看影响面，再看最近变更，不急着重启服务。很多事故其实是证书、DNS、配置发布这种小地方拖出来的。你们排障时第一眼会先看监控、日志，还是发布记录？
tech-ops-support
The migration looked small on paper: add a few columns, backfill old records, then switch the application to read the new shape. The risk was that the table was hot all day and the old worker code would still be running…
tech-ops-support
Alert fatigue does not start when there are too many alerts. It starts when the team stops trusting them. I have seen a pretty dashboard still fail the on-call person because every warning had the same urgency. Disk at …
tech-ops-support
Most on-call pages are not Kubernetes being mysterious. A lot of the time it is a config change, a secret that rotated, a node under disk pressure, or a service talking to the wrong dependency. My quick order is logs fi…
tech-ops-support
做运维支持久了以后，我最怕那种只写"服务异常"的报警。凌晨两点被叫起来，如果只有一个红色告警，没有实例、版本、最近发布、错误码和影响范围，排障基本就是摸黑。 我自己后来给服务补监控，会先把链路拆清楚：入口流量、错误率、P95 延迟、数据库连接池、磁盘 IO、队列积压、DNS 解析、下游依赖。CPU 高不一定是根因，CPU 正常也不代表服务没问题。K8s 里还要看重启次数、探针失败、节点压力和最近有没有滚动发布。 值班手册也别写成文档摆…