MetriBeacon
Menu
English
Sign inGo to account

Keep scheduled tasks in view

Scheduled jobs. Clear results.

See runtimes and failures. Get an alert when a scheduled job doesn’t start.

Go to accountRead the cronjob setup guide
Free to use · view quotas
Your monitor at a glanceExample data

Expected daily execution

  • job-104Scheduled
    Duration
    —
  • job-103Start missing
    Duration
    —
  • job-102Failed
    Duration
    12 s
    Exit code
    1
  • job-101Succeeded
    Duration
    45 s

What you can monitor

Every run at a glance

Follow your commands from start to result.

Execution status

See started, succeeded, failed and aborted executions.

Run times

Compare reported runtimes. Missing durations remain unknown.

Errors and exit codes

Use results and exit codes to investigate failures.

Missing runs

Detect missing starts using the saved cron schedule.

Understand your data

Know whether your job ran

Track starts, results and duration. A cron schedule detects missing starts; paused monitors pause these expectations.

Read the cronjob setup guide
Your monitor at a glanceExample data

Expected daily execution

  • job-104Scheduled
    Duration
    —
  • job-103Start missing
    Duration
    —
  • job-102Failed
    Duration
    12 s
    Exit code
    1
  • job-101Succeeded
    Duration
    45 s

Your first steps

Connect a job in three steps

Connect your source in three steps.

  1. 01

    Create a job monitor

    Create a job monitor in your workspace and copy its ID for the connection.

  2. 02

    Wrap your command

    Run your command through the MetriBeacon CLI so it can report the start and result.

  3. 03

    Add a schedule and alert

    Save the expected cron schedule and configure the appropriate alert rule.

Good to know

Frequently asked questions

Answers and setup guides.

How are missing executions detected?
A saved cron schedule tells MetriBeacon when your task should start. Without a schedule, the monitor shows reported runs. Paused monitors do not expect new starts.
Does a successful run verify my backup?
A successful run shows the result reported by your command. Check backup contents and restoration in your own backup process.
What happens when runtime is missing?
If your command does not report a duration, the history marks it as unknown.

Your next step

Make your next scheduled run visible

Connect your command and check its next run.

Go to accountRead the cronjob setup guide