HackerNoon

Your CI Pipeline Should Reject Any Service Without an Observability Contract (opens in new tab)

A payment notification service on our EKS cluster failed silently for 47 minutes — PagerDuty never fired, Loki never alerted, we found out from a customer tweet. The root cause was a microservice extraction that lost the structured logging config. The fix wasn't more tooling. It was treating observability as a hard deployment requirement, enforced with an Open Policy Agent policy in CI. Here's the Rego, the GitHub Actions gate, and the before/after of what changed.

Read the original article
Sign in to keep reading the full article.

Keyboard Shortcuts

Navigation

Next / previous post
j/k
Open post
oorEnter
Preview post
v

Post Actions

Love post
a
Like post
l
Dislike post
d
Undo reaction
u
Save / unsave
s

Recommendations

Add interest / feed
Enter
Not interested
x

Go to

Home
gh
Interests
gi
Feeds
gf
Likes
gl
History
gy
Changelog
gc
Settings
gs
Discover
gb
Search
/

General

Show this help
?
Submit feedback
!
Close modal / unfocus
Esc

Press ? anytime to show this help