基础设施与运维
ansible-playbook-logging
更新于 2026-10-30
Ansible · 日志规则
Logging rules for Ansible: structured fields, correlation ids and single-boundary failure logging.
- 技术栈
- Ansible
- 主题
- 日志
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Log structured key/value pairs, not interpolated prose
- ✓ Attach a correlation id shared by every hop of one request
- ✓ Log once at the failure boundary, not at every layer it passed through
✕ 常见反模式
- ✕ Logging full payloads that may contain personal data
- ✕ Debug-level spam left enabled in production configuration
- ✕ Log statements as the only signal for a metric-worthy event
◎ 交付前验证
- ◎ `plan` shows only the intended changes
- ◎ Policy checks (tags, encryption, public exposure) pass
- ◎ Rollback path for stateful resources documented
同分类条目
38 篇基础设施与运维
Docker 工程规则
Production Dockerfile rules: minimal multi-stage images and non-root runtime
基础设施与运维
Docker Compose 工程规则
Compose rules: explicit healthchecks, pinned images and network segmentation
基础设施与运维
Kubernetes 工程规则
Kubernetes rules: resource limits, readiness probes and rolling-update safety
基础设施与运维
Helm 工程规则
Helm rules: values schema validation and template-time guard rails
基础设施与运维
Terraform 工程规则
Terraform rules: locked remote state, reviewed plans and no console drift
基础设施与运维
Ansible 工程规则
Ansible rules: idempotent tasks, changed_when discipline and vaulted secrets