01
Check the response that matters.
Watch API status codes, response time and supported JSON rules. Define what healthy means for your endpoint.
Explore API monitoring FOR SAAS TEAMSKeep your product moving.
Keep your product moving.
Keep your customers informed.
Your homepage is only one part of the product. Watch the API behind it, the machines running it and the jobs that keep everything moving, with a clear place to share what happens next.
Monitor types and allowances depend on your plan. View plansacme / production
Websiteapp.example.com
OperationalPublic APIapi.example.com/health
Slow responseApplication hostproduction-01
HealthyNightly syncLast successful check-in
ReceivedAn available homepage is only the beginning.
A healthy landing page can sit in front of a failing API or a background job that stopped running. Build monitoring around the services your customers depend on, so a single green check does not stand in for the whole product.
02
Put the machine in the picture.
Review CPU, memory, disk and load alongside external availability checks when investigating a slow service.
Explore host monitoring03
Notice the work that goes quiet.
Add a heartbeat after a successful sync, report or backup. A missed check-in gives background work its own signal.
Explore heartbeats04
Give customers a place to look.
Publish selected services on a status page and share incident or maintenance updates where your plan supports them.
Explore status pagesA WORKFLOW YOU CAN MAKE YOUR OWN
A useful path through an interruption.
Start with a useful signal. Make ownership clear. Check how failures and recovery reach the people who need to act.
Find your setup guide- 01
Detect a meaningful change.
Set response rules and consecutive-failure thresholds for the product's critical endpoints.
- 02
Investigate with context.
Compare the failed check with related host and background-job signals. Choose alert recipients before an incident.
- 03
Keep the update moving.
Share the impact and next update on your status page, then follow the recovery signal in your workspace.
YOUR FIRST FEW SIGNALSA practical
A practical
starting point.
Add coverage in useful steps.
Keep each check understandable.
BEFORE YOU GET STARTEDA little context.
A little context.
Clearer decisions.
Practical answers for choosing the checks and workflow that fit.
Browse the documentationWhich checks should a SaaS team start with?+
Start with the customer-facing app and a health endpoint that reflects a critical service. Add host monitoring and heartbeats for background work where those signals help explain failures. Check your plan for available monitor types and allowances.
Does an API check test the whole user journey?+
An API or website check validates supported HTTP behavior and response rules. It does not run a full browser journey or prove that every customer workflow works. Choose endpoints that give a useful signal about the behavior you need to monitor.
Can we share availability with customers?+
Yes. A status page can present selected service availability. Incident updates, maintenance communication and other status-page options depend on the features enabled for your plan.
Will monitoring diagnose the cause automatically?+
Checks show the behavior they observe. Related host, API and job signals can help your team investigate, but they do not establish a root cause on their own.
START WITH ONE IMPORTANT SERVICEA clearer view.
A clearer view.
For your kind of work.
Choose your first check. Build the context around it.