See every job. Catch every failure.

# Install CronitorCLI on the box that runs your jobs
$ curl https://cronitor.io/install-linux?sudo=1 -H "API-KEY: <API-KEY>" | sh

# Walk the crontab and add monitoring to the jobs you choose
$ cronitor sync
----► Scanning for cron jobs...
 |--► Found 15 jobs in user "ec2-user" crontab
 |--► Send Daily Reports   │ ✔ Monitor this job
----► Sync complete ✔

# Your crontab comes back instrumented. Status, duration and output
# are reported for you — the job itself never changes.
0 9 * * * cronitor exec send-invoices "/usr/local/bin/send-invoices.sh"

# Add the Cronitor Helm chart
$ helm repo add cronitor https://cronitorio.github.io/cronitor-kubernetes/

# Add your Cronitor API key as a Secret
$ kubectl create secret generic cronitor-secret -n <namespace> \
    --from-literal=CRONITOR_API_KEY=<API-KEY>

# Deploy with Helm 2 or Helm 3 — every CronJob on the cluster syncs
$ helm upgrade --install <release-name> cronitor/cronitor-kubernetes \
    --namespace <namespace> \
    --set credentials.secretName=cronitor-secret \
    --set credentials.secretKey=CRONITOR_API_KEY

# Run PowerShell as Administrator to install CronitorCLI
Invoke-WebRequest -Uri "https://cronitor.io/dl/windows_amd64.zip" `
  -OutFile "$env:TEMP\cronitor.zip"
Expand-Archive -Path "$env:TEMP\cronitor.zip" `
  -DestinationPath "$env:ProgramFiles\Cronitor" -Force
Remove-Item "$env:TEMP\cronitor.zip"
[Environment]::SetEnvironmentVariable("Path", `
  "$env:Path;$env:ProgramFiles\Cronitor", "Machine")

# Open a new terminal so the PATH takes effect, then configure
cronitor configure --api-key '<API-KEY>' --api-version '2025-11-28'

# Walk Task Scheduler and monitor the tasks you choose
cronitor sync

# Install the CLI into the image that runs the job
FROM python:3.12-slim
RUN curl -sOL https://cronitor.io/dl/linux_amd64.tar.gz \
 && tar xf linux_amd64.tar.gz -C /usr/bin/

# Wrap the container command — exit status, duration and output ship home
ENTRYPOINT cronitor exec -k $CRONITOR_API_KEY nightly-export \
  "python /app/export.py"

# Pass the key in at run time, never bake it into the image
# docker run -e CRONITOR_API_KEY=<API-KEY> nightly-export

# Add Cronitor to your project
$ pip install cronitor

# Configure once, at startup
import cronitor
cronitor.api_key = '<API-KEY>'

# Decorate anything scheduled — start, finish, duration
# and unhandled exceptions are all reported
@cronitor.job('send-invoices')
def send_invoices():
    Invoices.objects.send_all()

# Celery support ships inside the Python SDK
$ pip install cronitor

# Configure, then register your Celery app once
import cronitor.celery
cronitor.api_key = '<API-KEY>'

cronitor.celery.initialize(app)

# Every task is now monitored. To watch only the beat schedule:
cronitor.celery.initialize(app, celerybeat_only=True)

// Add Cronitor to your project
$ npm install cronitor

// Configure with your API key
const cronitor = require('cronitor')('<API-KEY>');

// Wrap any function with telemetry events
cronitor.wrap('send-invoices', function () {
    console.log('running background job with monitoring!');
});

// Or embed telemetry events directly in your code
const monitor = new cronitor.Monitor('send-invoices');
monitor.ping({state: 'run'});

# Add Cronitor to your project
$ gem install cronitor

# Import and configure
require 'cronitor'
Cronitor.api_key = '<API-KEY>'

# Wrap any block with telemetry events
Cronitor.job 'daily-metrics' do
  DailyMetricsJob.new(Date.today).run
end

# The Sidekiq middleware is its own gem
$ gem install sidekiq-cronitor

# Configure Cronitor and register the server middleware
require 'cronitor'
Cronitor.api_key = '<API-KEY>'

Sidekiq.configure_server do |config|
  config.server_middleware do |chain|
    chain.add Sidekiq::Cronitor::ServerMiddleware
  end
end

# Periodic jobs: Sidekiq::Cronitor::PeriodicJobs.sync_schedule!

// Add Cronitor to your project
$ composer require cronitor/cronitor-php

// Import and configure
$cronitor = new Cronitor\Client('<API-KEY>');

// Wrap any invokable class or function
$cronitor->job('weekly-report-job', new WeeklyReport);

$cronitor->job('weekly-report-job', function() {
    (new WeeklyReport)->send();
});

# Install the Laravel SDK
$ composer require cronitor/laravel

# Add your API key to your .env file
CRONITOR_API_KEY='<API-KEY>'

# Sync monitors during deploy
$ php artisan cronitor:sync

# All set — your scheduled tasks and queue jobs are monitored
# automatically from here on.

# Tell Cronitor a job started, finished, or failed
$ curl https://cronitor.link/p/<API-KEY>/send-invoices?state=run
$ curl https://cronitor.link/p/<API-KEY>/send-invoices?state=complete
$ curl https://cronitor.link/p/<API-KEY>/send-invoices?state=fail

# A key that doesn't exist yet is created on its first ping

# Attach metrics and a message to any ping
$ curl "https://cronitor.link/p/<API-KEY>/send-invoices?state=complete\
&metric=count:1204&metric=duration:41.2&message=Import+complete"

# Metrics: count, error_count, duration, latency, length, tokens, actions, cost