Nightly AI Pipeline
FailedSchedule
0 2 * * *
Uptime
45%
Last ping
Jan 15, 2026, 4:49 PM
Track scheduled LLMLLMA large language model is a text-focused AI model trained on large amounts of data to understand, generate, summarize, translate, or reason over language.View glossary entrySource: Google Cloud Generative AI glossary batchesbatchA group of records or tasks processed together. Batch jobs are often monitored by counting processed items, failed items, duration, and cost.View glossary entrySource: Anthropic API overview, random agentagentAn AI application that uses a model, instructions, state, and tools to work toward a goal. Agents are useful to monitor because they can run for a while and make multiple tool calls.View glossary entrySource: Google Cloud Generative AI glossary workersworkerA background process that performs work outside the main request path, such as syncing data, generating reports, or running AI tasks.View glossary entrySource: GitHub Actions CI docs, RAG syncsRAGRetrieval-augmented generation improves model output by retrieving relevant information from a knowledge source and grounding the response in that context.View glossary entrySource: Google Cloud Generative AI glossary, eval runsevalA test or scoring run used to judge whether an AI system behaved well enough. TelemHQ can track eval score, pass rate, failures, and regressions.View glossary entrySource: Google Cloud Generative AI glossary, and AI reports with heartbeatheartbeatA lightweight signal that proves a job checked in. TelemHQ extends heartbeats with payload data so the run can explain what happened.View glossary entrySource: TelemHQ docs pingspingA request sent to TelemHQ after a job runs. A ping can be a simple heartbeat or include JSON payload data about what happened.View glossary entrySource: TelemHQ docs plus structured payloadpayloadThe structured data sent with a request. In TelemHQ, payloads should contain safe operational metadata, not prompts, completions, secrets, customer data, or private paths.View glossary entrySource: MDN API glossary data. Use it solo, or invite teammates so managers can see project-level tokenstokensThe pieces of text an AI model processes. Token counts are often used to measure usage and calculate model cost.View glossary entrySource: OpenAI token guide, spendcostThe money associated with a run, often estimated from token usage and provider pricing. TelemHQ can store cost fields when your job sends them.View glossary entrySource: OpenAI token guide, failures, and per-user activity in one place.
See which runs fired, what project they belonged to, who ran them, how many tokens they consumed, and whether the payload passed your checks.
LLM pipelines, evals, agents, reports, and classic cron jobscron jobA scheduled task that runs automatically, often on a server. TelemHQ tracks cron jobs by receiving a ping after each run.View glossary entrySource: AWS EventBridge Scheduler docs in one view
Schedule
0 2 * * *
Uptime
45%
Last ping
Jan 15, 2026, 4:49 PM
Schedule
*/30 * * * *
Uptime
98.7%
Last ping
Jan 10, 2026, 6:49 PM
Schedule
No schedule
Uptime
100%
Last ping
Jan 15, 2026, 6:49 PM
0 2 * * *
Last ping
Jan 15, 2026, 4:49 PM
Uptime
45%
*/30 * * * *
Last ping
Jan 10, 2026, 6:49 PM
Uptime
98.7%
No schedule
Last ping
Jan 15, 2026, 6:49 PM
Uptime
-
| Name | Status | Owner | Schedule | Last Ping | Uptime | Actions |
|---|---|---|---|---|---|---|
| Nightly AI Pipeline | Failed | - |
0 2 * * *
|
Jan 15, 2026, 4:49 PM | 45% | |
| RAG Index Sync | Active | - |
*/30 * * * *
|
Jan 10, 2026, 6:49 PM | 98.7% | |
| Agent Tool Worker | Active | - | No schedule | Jan 15, 2026, 6:49 PM | - |
TelemHQ turns numeric JSONJSONA common text format for structured data. TelemHQ accepts JSON payloads so jobs can report fields like status, tokens, duration, and cost.View glossary entrySource: MDN glossary payload fields into charts automatically. Pin the metrics you care about, filter by project, switch between individual and combined charts, and inspect complete history when you need more than the latest runs.
0 2 * * *
Every day at 2:00 AM
• Next: Jan 16, 2026, 12:00:00 AM
(in 8m)
modelmodelThe AI system that processes input and returns output. For monitoring, the model name helps explain which tool or provider produced a run and how its token usage should be priced.View glossary entrySource: Anthropic model docs: gpt-5, tokens: 9,060
items_processed: 128
model: claudeClaudeAnthropic’s family of AI models. TelemHQ can track Claude jobs by recording model names, token usage, latency, cost, and run metadata.View glossary entrySource: Anthropic model docs-sonnet-4
latency_ms: 2,140
| Time | Summary | |
|---|---|---|
|
9 FIELDS
model:
gpt-5, tokens: 9060, ...
|
||
|
6 FIELDS
items_processed:
128, eval_score: 0.91
|
||
|
6 FIELDS
model:
claude-sonnet-4, items_failed: 0
|
||
|
6 FIELDS
latency_ms:
2140, status: success
|
Total Tokens summed across recent pings.
Input Tokensinput tokensTokens sent into a model as input. Tracking them helps teams understand how much context each run consumed.View glossary entrySource: OpenAI token guide
7.9M
Cached Input
4.1M
Output Tokensoutput tokensTokens produced by a model as output. They are part of total usage and are often priced separately from input tokens.View glossary entrySource: OpenAI token guide
318K
Payload intelligence
TelemHQ detects numeric payload fields such as total tokens, cached input tokens, latencylatencyHow long a request or job takes to respond. AI job latency helps teams spot slow model calls, overloaded workers, or expensive retries.View glossary entrySource: MDN glossary, cost, failures, and eval scores, then charts them automatically for every future ping.
Use recommended charts or choose your own fields. TelemHQ keeps charting them automatically.
Break down token usage by project, then see which teammates contributed the most runs, tokens, and cost.
Opt in per tracker for deterministic summaries of yesterday or the previous seven complete days.
Team insights
Team plans let multiple people send pings from their own trackers while managers get a combined view of usage across teammates, projects, models, tokens, spend, failures, and active times.
If three teammates work on the same project, TelemHQ combines the project and shows each member's contribution underneath it.
Members keep their own trackers, while managers can inspect team usage, drill into a member, and manage seats or access.
Teams are billed per active member, and revoked members stop adding data without losing historical usage.
Team workspace
Team-level usage by project and member
Members
8
Runs
3.2K
Tokens
41M
Spend
$842
3 contributors - 1.9M tokens - $406.13 spend
Some AI work runs on a cron schedule. Some runs whenever a webhookwebhookAn HTTP callback sent when an event happens. TelemHQ can use outgoing webhooks to notify another system about tracker events.View glossary entrySource: MDN API glossary, queue, or user action triggers it. TelemHQ supports both without forcing every tracker into a timer.
Send JSON with every ping: model, tokens, latency, cost, output counts, eval scores, and your own fields.
Add a cron schedule for jobs that should run on time. Leave the schedule blank for random or triggered work, and TelemHQ will not fail it for missed pings.
Mark a tracker as failing when status is not success, zero items are processed, costs exceed budget, or eval scores drop.
No TelemHQ SDKSDKA software development kit is a package of tools or libraries for building with a platform or API.View glossary entrySource: MDN API glossary required. Add one POSTPOSTAn HTTP method used to send data to a server. TelemHQ pings use POST when a job reports a run and optional payload.View glossary entrySource: MDN HTTP docs request to OpenAIOpenAIAn AI provider whose APIs and models are commonly used for text generation, coding, reasoning, embeddings, and agent workflows.View glossary entrySource: OpenAI token guide, Claude, cron, queue, or worker code.
Track operational metadatametadataData about a run rather than the private content of the run itself, such as model name, duration, branch, item counts, or token totals.View glossary entrySource: MDN API glossary without sending prompts, completions, retrieved documents, or customer content.
Use cron expressionscron expressionA compact schedule string made of time fields, such as minute, hour, day, month, and weekday. It describes when a recurring job should run.View glossary entrySource: AWS EventBridge Scheduler docs for nightly batches, hourly syncs, and weekly reports, or no schedule for queue workers, webhooks, agents, and other event-driven jobs.
Auto-chart numeric payload fields, choose 50 recent runs or complete history, and compare model behavior, latency, throughput, and cost over time.
Include a project field in each ping to see which codebase, customer workflow, agent, or service is using the most tokens.
Opt in to daily or weekly tracker summaries with run counts, token totals, model mix, cache efficiency, failure rate, and outliers.
Track model, token usage, latency, output counts, and cost per run
Track documents embedded, chunks updated, failures, and duration
Track pass rate, score thresholds, regressions, and failed cases
Track rows processed, skipped records, provider errors, and retries
Monitor report size, processing time, status, and source coverage
Track background agents, tool-call workers, and triggered automations without requiring a schedule
Start free, upgrade solo, or add teammates at $10 per user.
Perfect for hobby projects.
For serious applications.
For teams tracking AI usage together.
Track scheduled and ad hoc LLM pipelines with payload data, assertions, and alerts. Free forever for up to 5 trackers.
Start for free