/features/alerts
log + metric + trace + webhook
free plan / 1 gb-mo
telemtra.io
// feature

Alerts that fire on what
actually matters.

A customer just hit a 500 error. They have not filed a ticket yet - but you already got the webhook. By the time they email support, your on-call is already debugging the trace.

// one alerting model

One alerting model across every signal.

Why does your log alert tool not talk to your metric alert tool? Telemtra evaluates log patterns, structured fields, trace latency, and metric thresholds on the same schedule and delivers them through the same channels. One screen to write a rule, one history to audit it.

  • Log alert rules on matching log streams
  • Structured log field alert rules (e.g. status_code = 500)
  • Trace percentile latency rules (p95, p99)
  • Metric threshold rules with per-dimension evaluation
// audit every delivery

Delivery you can trust and debug.

When something fires at 3 AM, the on-call needs to know exactly what was sent and where. Every alert has a full delivery record - webhook responses, HMAC verification, email sends, with timestamps. Send a webhook test before you depend on it.

  • Email delivery to your team
  • Webhook delivery with HMAC signing
  • Send a webhook test before you depend on it
  • Full alert delivery history
  • Enable or disable any rule without deleting it
// built to stay meaningful

Rules that age well.

The metric-name picker is scoped to services and time ranges you have actually observed, so you alert on signals that exist - not guesses.

→

Observed-only pickers

Metric and field dropdowns are scoped by the services and time range you have actually sent, so rules target real signals.

→

Per-dimension evaluation

Metric thresholds can evaluate per host or attribute, so one noisy instance does not hide behind a healthy average.

→

Plan-based intervals

Alert evaluation frequency scales with your billing plan. See pricing for the interval per plan.

// works with

Connects to.

// frequently asked

Questions about alerts.

What can I create an alert on?

Log patterns, structured log field values, trace p95 / p99 latency for any service-operation pair, and metric thresholds (gauge, counter, or histogram percentile).

Where are alerts delivered?

Email and signed webhooks. Webhook payloads include a signature header so receivers can verify the alert came from Telemtra.

How often do alerts evaluate?

Per plan. Free evaluates on a slower schedule; Solo and Team evaluate faster. Each rule shows its actual evaluation interval in the workspace.

Can I see past alert deliveries?

Yes. Every rule has a full delivery history with timestamps, payloads, and webhook responses, so you can audit what fired and when.

Can I silence an alert during planned maintenance?

Yes. Disable the rule from its detail page; re-enable when maintenance ends. No data is lost, only the firing behavior is paused.

// next step

Get alerted before your users notice.

Create a workspace, send telemetry, set your first alert in minutes.