以下の詳しいガイドと説明用の事例は英語です。例に含まれる業務データは架空のものです。
Where Prometheus fits
Operational metrics that lead to a specific action when service health deteriorates.
When to choose another approach
Metrics do not supply staffed support or detection of every incident.
Worked example and evidence
Fictional API: failed-request ratio exceeds an agreed threshold for five minutes → alert → nominated engineer checks dependencies → business owner receives an impact update. Timing is illustrative.
What you need to supply
Critical journeys, metric endpoints, normal traffic, escalation contacts and coverage hours.
What acceptance should demonstrate
Simulate a failure, confirm delivery, follow the runbook and verify recovery clears the alert.
Running costs and responsibilities
Own storage, retention, alert tuning and responder availability. Exclude customer identifiers from labels.
Technical scope to confirm
Alert on actionable symptoms. Missing metrics and monitoring failures also need handling.
A proposal should identify the systems and data, direction of sync, access feasibility, failure handling, named owners and included deliverables. Listing this technology does not imply a prebuilt connector, vendor partnership or included feature.
Which failures should page someone?
Page for defined urgent impact with a responder who can act. Put non-urgent trends in a review queue.