Lack of Continuous Monitoring Tools

“Ask HN: How do you detect configuration drift between environments? Hi HN,<p>I’m curious how teams detect configuration drift between environments like prod, staging, and test.<p>In several projects I worked on, incidents were often caused by unnoticed config differences between environments. Usually someone changed a config, a deployment happened later, and the difference went unnoticed until something broke.<p>Most tools I found focus on file diff, but not on monitoring drift over time.<p>Because of that, I started building a small tool around this idea:<p>- configuration is scanned from a Git repository - a baseline run defines the expected state - scheduled scans compare configs against that baseline - drift opens a finding - alerts can be delivered to Slack or Jira<p>Manual runs are mainly for inspection. Scheduled runs are intended for monitoring.<p>Typical examples include: - .NET appsettings.json - IIS &#x2F; web.config - environment-specific configs across multiple environments<p>I’d love to hear how others currently solve this problem in practice.<p>Live: https:&#x2F;&#x2F;gatewaylabs.net”