Skip to content
Facteur

Your messaging tests are a signal like any other

A testing tool that does not observe itself lets you discover its limits at the same time as the outage. Facteur tells you what you use, and warns you before the limit.

GET /messages/{id} JSON
{
  "id": "0ndqut25td20dah7",
  "inbox": "j3k9x2mq",
  "type": "email",
  "receivedAt": "2026-10-02T09:15:31+00:00",
  "deliveryMs": 38,
  "status": "quota_exceeded",
  "errorCode": "INBOX_QUOTA_EXCEEDED"
}
A refused message leaves a trace: its code says which ceiling stopped it. The search shows it with status=any.
webhook payload JSON
{
  "type": "quota.threshold",
  "data": {
    "organizationId": "acme",
    "scopeKind": "organization",
    "scopeId": "acme",
    "family": "quota",
    "threshold": 80,
    "used": 160000,
    "ceiling": 200000,
    "periodStart": "2026-10-01"
  }
}
The shape of the event is fixed. The platform that sends webhooks is not open yet: none leaves today.

What Facteur already tells you

01

Alerts before the limit

80 · 100 %

Facteur writes to you at 80 % and then 100 % of the period's volume, when the pace announces running out before the end of the period, when a single day uses too much and when attachment storage passes 80 %. With no setting on your side.

02

Your thresholds, your recipients

Add up to four thresholds of your own, and up to three email addresses on top of the administrators. An alert leaves once per threshold crossed and per period.

03

Who used it, and when

The usage screen shows what each inbox received and refused over the period, and the organisation's usage day by day.

04

A refusal that gives its reason

errorCode

A refused message is not swallowed in silence. It leaves a trace with its code: the ceiling of the inbox, of the workspace or of the plan, the spending cap, the daily limit. Your test reads it through the API.

05

The reception time of each message

deliveryMs

Each message carries the time the reception service took to accept it, in milliseconds. Your test can put a limit on it, or record it to follow the trend.

What is not available yet

Each line describes today's state. None of these outputs works yet.

01
Not yet

Signed webhooks

Every kept message and every alert will be able to call your server. The screen where you will declare your addresses exists in the application, but the sending platform is not open: no webhook leaves today.

02
Not yet

Microsoft Teams

An alert in a Teams channel will go through a webhook. As long as webhooks do not leave, Teams is not offered: email is, on every plan, and Slack, Discord, PagerDuty and OpsGenie from Solo up.

03
Not yet

Prometheus endpoint

Your volumes, how full your ceilings are and your reception times, scraped by Prometheus into the same Grafana as everything else. This endpoint does not exist today.

04
Not yet

OpenTelemetry export

Metrics pushed to an OpenTelemetry collector, and so to most observability platforms. This export does not exist today.

05
Not yet

Datadog integration

Metrics and events sent into your Datadog organisation, to correlate an overage with your deploys. This integration does not exist today.

06
Not yet

Reception time as a metric

A reception time published as a metric you monitor. Today, it is read message by message, in the deliveryMs field.

A quota you do not see coming is an incident

A common scenario, and what an alert changes in it.

  1. 01

    A test suite is changed on a Monday. It now sends three times more emails than before. Nobody notices: it is an implementation detail.

  2. 02

    On Tuesday at 11 am the inbox's daily ceiling is reached. The next messages are refused.

  3. 03

    CI turns red on tests nobody touched. The team hunts for the regression for two hours before thinking of the quota.

With an alert threshold at 50 %, that Monday an email reaches the team's address. The overage becomes a decision (buy a pack, review the test) instead of an investigation.

Be told before the limit

Usage alerts leave from the moment the account exists, with no setting. Thresholds and recipients are then set in the application.