Metrics, uptime checks, error tracking, alerts and the activity log.
Once a minute it connects over SSH, reads the figures from the operating system and disconnects again. You install no agent. The results appear as tiles and charts on the server's Monitoring tab. See Read your server's metrics and charts.
The newest reading is more than three minutes old, usually because SrvYard cannot reach the server. Stale numbers describe the past, so fix the connection first. Gaps in a chart never change the state of a monitor. See Read your server's metrics and charts.
No. It does not poll your public site on a timer. Instead, heartbeats tell you when a scheduled task stops, and a health check runs after every deployment. See Get told when a scheduled task stops running and See how a site is doing with Observe.
A URL that your cron job or script requests when it finishes. If a ping does not arrive within the frequency plus your wait, the heartbeat is missed and owners and admins are notified. It catches silent failures such as a scheduler that never started. See Get told when a scheduled task stops running.
Create a server monitor with a threshold and a duration, such as 90 per cent for five minutes, and choose who is told. It needs a plan with server monitoring, and a server can have at most 20 monitors. See Get alerted when CPU, memory or disk run hot.
Yes. Add a notification channel for Slack, Discord, Telegram or email, then filter it by event, severity and scope. An organisation can have 20 channels. See Send alerts to Slack, Discord, Telegram or email.
The activity feed keeps the last 14 days and cannot be switched off. If you need a longer record, copy what you need or fetch it through the API on a schedule. See Find out what happened with the activity log.
Yes, by connecting a Laravel site to TraceBeat or Nightwatch. SrvYard writes the settings into the .env and runs the agent, but you add the laravel/nightwatch package to your own code. See Send requests, jobs and exceptions to TraceBeat or Nightwatch.