The agent, what does it do?

Posted on Mar 26, 2026
tl;dr: The agent sends to tinyfal the metrics you want it to.

The agent

The install.sh script just sets up agent.sh in "$HOME/.tinyfal". It contains the following:

#!/bin/sh
# Tinyfal Agent
# This script is run every minute by cron.

set -u

URL="https://ingest.tinyfal.com"
SENT_AT=$(date -u +%s) # timestamp seconds since Epoch
REQUEST_AT_UTC=$(date -u +"%Y-%m-%d %H:%M:%S UTC")
PAYLOAD=$(printf '{"metrics": {"escohotado":0},"sent_at": %s}' "$SENT_AT")
echo "Request time: ${REQUEST_AT_UTC}"
curl -sS \
    --max-time 10 \
    -w '\n' \
    -X POST \
    -H "Authorization: Bearer $1" \
    -H "Content-Type: application/json" \
    -d "${PAYLOAD}" \
    "${URL}" || true

The payload

In the metrics field, add the values you want to send to your dashboard. Only those fields inside metrics will be saved.

Why this instead of a telegraf agent?

We think that you have now enough resources to send to your monitoring dashboard exclusively what you need from your server. No bloat, no slop, just send what you need.

The rules

For now, the backend accepts requests only if they follow these rules:

  • The metrics payload can have up to 5 fields. I will add more at some point.
  • Nested objects are not allowed.

I want to keep cloud costs under control while this is still early.

If this works well, I will add paid plans later.

If you need more, contact me at:

fernando@tinyfal.com