Output Search

Overview

Output Search helps you find text inside the output attached to previous pings. When your jobs send stdout, stderr, JSON payloads, or log snippets to Cronping, you can search that captured output from the dashboard instead of opening each heartbeat run one by one.

Use Output Search when you need to answer questions like:

• Which job emitted connection refused?
• Did any pipeline log rows_processed: 0?
• Which heartbeat reported a specific customer ID, order ID, file name, or batch ID?
• Did a warning appear before the heartbeat went down?

Send searchable output

Output Search works with ping request bodies. Send output with POST when your job pings Cronping:

OUTPUT=$(/usr/bin/backup.sh 2>&1)
curl -fsS -m 10 \
  --data-raw "$OUTPUT" \
  https://ping.cronping.com/<token>/$?

You can also attach logs without changing the heartbeat status by using /log:

curl -fsS -m 10 \
  --data-raw "Processed 42,391 records in 18.4s" \
  https://ping.cronping.com/<token>/log

See Attaching Logs for more examples and size limits.

Search across the organization

Go to Organization > Output Search to search captured output across all heartbeats in the active organization.

The results show:

• Ping type, such as success, fail, warn, log, or start.
• Heartbeat name.
• Received timestamp.
• A snippet around the matching text.
• A link back to the heartbeat.

You can filter by ping type to focus on failures, warnings, log entries, or successful runs.

Search a single heartbeat

Open a heartbeat detail page and use Search Ping Output to search only that heartbeat's captured output.

This is useful when you already know which job failed and want to find the relevant run output quickly.

What to put in ping output

Good searchable output is short, structured, and specific.

Prefer including:

• Error messages and stack traces.
• Row counts, file names, batch IDs, and customer IDs.
• External service names and response codes.
• Job duration and high-level stage names.
• JSON summaries that can also power alert rules.

Avoid sending secrets, access tokens, private keys, or full raw logs that belong in a dedicated log storage system.

Limits

Cronping stores up to 100 KB of request body per ping. If your output is larger, send the most useful summary or truncate to the end of the log where failures usually appear:

OUTPUT=$(/usr/bin/backup.sh 2>&1 | tail -c 100000)
curl -fsS -m 10 --data-raw "$OUTPUT" https://ping.cronping.com/<token>/$?

For long-term log retention, keep your full logs in a logging platform and use Cronping for status, alerts, and searchable run context.