What would you monitor for Decorators on-call?

Answers use simple, clear English.

Quick interview answer

On-call for Decorators: alert on lag/latency, error spikes, and saturation — with runbooks. Common mistakes: Forgetting @wraps; decorator not returning wrapper function. Best practices: Use wraps; accept *args/**kwargs in generic decorators; prefer parameterized factory pattern.

Detailed answer

On-call monitoring for Decorators: • Golden signals: latency, traffic, errors, saturation • Decorators-specific gauges (queue delay, pool wait, cache miss, etc.) • Alerting: burn-rate / multi-window so pages are actionable • Runbook: mitigate → diagnose → escalate Parent context: Common mistakes: Forgetting @wraps; decorator not returning wrapper function. Best practices: Use wraps; accept *args/**kwargs in generic decorators; prefer parameterized factory pattern.

Full explanation

Tie each alert to a user-visible or SLO impact for Decorators. Common mistakes: Forgetting @wraps; decorator not returning wrapper function. Best practices: Use wraps; accept *args/**kwargs in generic decorators; prefer parameterized factory pattern.

Follow-up questions

Only answered follow-ups are shown — click to open with full answers

Parent context — Decorators

Common mistakes: Forgetting @wraps; decorator not returning wrapper function. Best practices: Use wraps; accept *args/**kwargs in generic decorators; prefer parameterized factory pattern.

View full parent question →

#py-decorators#senior