Onchain automation monitoring

How to test this use case

Measure Crypto and onchain automation monitoring and check the results

To measure crypto and onchain automation monitoring, choose one workflow and its owner. Define the events, test them with known inputs, and write a query that answers a specific question.

1
Choose when to log
Log indexer updates, agent runs, wallet actions, transaction attempts, and deploys.
2
Capture the outcome
Begin with indexer_update_completed, transaction_submitted, transaction_failed and document the grain of each event.
3
Check the stored rows
Create alerts around failed transactions, indexer stalls, and cost spikes.
4
Make the decision
Which automation workflows create the most failed transactions?

Agent prompt

Paste this into your coding agent

Replace YOUR_API_KEY after signup, then ask the agent to run the product flow and verify the first events.

agent prompt

Crypto and onchain automation monitoring setup prompt

text

Instrument crypto and onchain automation workflows with Telemetry.

Use /skill.md and this Telemetry API key: YOUR_API_KEY

Please log indexer updates, wallet actions, agent runs, tool calls, transaction attempts, deploys, gas costs, and failures. Include chain_id, network, workflow_name, wallet_category, status, latency_ms, gas_cost_native, gas_cost_usd, retry_count, and error_type where relevant.

Create dashboards for transaction failures, gas cost by workflow, indexer freshness, tool-call failures, and recent deploy activity.

Do not log private keys, signatures, mnemonics, raw auth tokens, or sensitive wallet owner data.

Setup steps

1Log indexer updates, agent runs, wallet actions, transaction attempts, and deploys.
2Capture chain, wallet category, status, gas cost, latency, and error type.
3Add SQL queries for failed actions, cost by workflow, and recent deployments.
4Create alerts around failed transactions, indexer stalls, and cost spikes.

Events to capture

indexer_update_completedtransaction_submittedtransaction_failedagent_run_completedtool_call_failedgas_cost_recorded

Questions you can answer

Which automation workflows create the most failed transactions?
Where are gas costs or retries increasing?
Which agents or tools are responsible for operator interventions?

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Async reliability11 fields