Content pfp
Content
@
https://warpcast.com/~/channel/devops
0 reply
0 recast
0 reaction

Thresh pfp
Thresh
@0xthresh
DevOps debate of the day: where should monitoring/ alerting live in IaC? Should it live close to the component being monitored (for example, defining a DataDog alert in the same folder as the AWS service it’s monitoring) or should monitoring definitions be placed somewhere separate so it can be managed together?
3 replies
0 recast
1 reaction

Lemma pfp
Lemma
@lemma
Depends on the internal team structure and engineering culture IMO. If lots of teams managing their own services, I’d say placing all IaC with that same service is going to mean less stepping on other teams toes in my experience.
1 reply
0 recast
1 reaction

Thresh pfp
Thresh
@0xthresh
I definitely expected an”it depends” response to this 😄 but that’s what I was thinking as well, there’s certain shared monitoring that I might keep separate but want to integrate service-specific checks into their existing modules.
1 reply
0 recast
1 reaction

Lemma pfp
Lemma
@lemma
What worked well for our team at previous job was the monitoring team had all the infra managed and exposed namespaced things to us so e.g. we managed our own alarms and graphs in IaC in our repo, and at build/deploy time it deployed to the infra they managed. Good compromise, and if we needed more levers we collab’d
2 replies
0 recast
1 reaction

Thresh pfp
Thresh
@0xthresh
That sounds like an awesome setup. Thanks for sharing so much detail, it helps a ton!
0 reply
0 recast
1 reaction