Alerting & Notifications

Alerting & Notifications

Deliver Fleetera alerts to your own systems, to Slack, and to PagerDuty or Jira Service Management.

When an alert triggers or resolves in Fleetera, you can have the platform notify an external system automatically. Notifications are sent through notification channels — destinations you configure once and reuse across your alerts.

A webhook channel is a channel that posts a signed JSON message to an HTTPS endpoint you control. Webhooks are the most flexible channel type: because Fleetera sends a structured, signed payload, you can route alerts into Microsoft Teams, a ticketing system, or any service that can receive an HTTP request.

For Slack there is a shorter path. A Slack channel takes a Slack incoming webhook URL and posts a formatted message straight into the channel, with no relay or payload mapping of your own — see Slack Notifications.

For on-call tools there are two native channel types. A PagerDuty channel and a Jira Service Management channel each open an incident (or an alert) in the tool when an alert fires, acknowledge it when the alert is acknowledged in Fleetera, and resolve it when the alert resolves. See PagerDuty and Jira Service Management.

Your notification preferences

For your own email and in-app alerts, open Settings → Notifications. You can choose a severity level, collect excluded alerts in a daily digest, and enable critical alert toasts. These preferences also govern assignment emails. See Notification Preferences for shared inbox behavior, collection windows, outage delays and possible duplicate digests after an unconfirmed delivery response.

Webhook delivery

  1. You create a webhook channel with the destination URL (and, optionally, custom headers).
  2. Fleetera generates a signing secret for the channel and shows it to you once.
  3. When an alert triggers — or resolves, if you opt in — Fleetera sends an HTTP POST to your URL with a JSON body describing the alert.
  4. Each request carries an HMAC signature computed with your channel secret, so your receiver can confirm the request genuinely came from Fleetera.
  5. If your endpoint is unavailable, Fleetera retries with exponential backoff before giving up.

The channel signing secret is shown only once, at the moment you create the channel. Fleetera stores it encrypted and can never display it again. Copy it immediately and store it like a password (in a secrets manager or your platform's environment configuration). If you lose it, create a new channel to get a new secret.

In this section

Alarm Policy

What each priority means and how fast it should be answered, the values new rules start from, and how often notifications repeat.

Webhook Notifications

Create a webhook channel, add custom headers, and understand the signing secret.

Webhook Payload Reference

The versioned JSON payload Fleetera sends, field by field, with examples.

Verifying Webhook Signatures

Authenticate requests with the HMAC signature, plus delivery and retry semantics.

Slack Notifications

Point a native Slack channel at an incoming webhook — no relay, no payload mapping.

PagerDuty

Trigger, acknowledge and resolve PagerDuty incidents from Fleetera alerts.

Jira Service Management

Open, acknowledge and close Jira Service Management Operations alerts from Fleetera alerts.

Connecting Other Destinations

Wire Fleetera webhooks into Teams and other destinations, and test your endpoint.

Availability

Read a contract period's time and production availability on the ledger basis, check that its bins reconcile, trace each event and export the rows.

Alarm Policy

Set what each alert priority means, the values new rules start from, how often notifications repeat, and your alarm load targets.

On this page

Your notification preferencesWebhook deliveryIn this section