sethfantastic, 18 days ago

@paigerduty gaps in alerting / monitoring, generally due to observability NFRs being left out of scope of projects or discovered post-facto but not resolved

paigerduty, 18 days ago

@sethfantastic ooh whats an NFR?

sethfantastic, 18 days ago

@paigerduty Non Functional Requirement

thejtoken, 18 days ago

@paigerduty to me this concept sounds like:

• The team can do it better (i.e. alerts accuracy, too much noise, etc)
• Alert fatigue

clark, 18 days ago

@paigerduty - Several things
1: I hope "monitoring debt" doesn't become a thing. We need more clarity and fewer noms-du-jour.

2: Failure to adopt and apply organizing principles to monitoring infrastructure that facilitate intuitive use and management over time.

aaronw, 18 days ago

@paigerduty Obsolete alerts (tracking outdated metrics or warning on outdated thresholds), missing alerts (not tracking important items), and the Splunk bill.

esg, 18 days ago

@paigerduty can't resist this joke:
The money I owe datadog / new relic / whatever else

bocytko, 18 days ago

@paigerduty 1) lots of alert definitions which once set up are forgotten or ignored; data series captured, written, but never looked at.

2. manual instrumentation code that's unnecessary as automation caught up or that was not properly adjusted during refactoring.