Stream real-time notification metrics from SuprSend to any OpenTelemetry-compatible observability platform via OTLP.
The SuprSend OTel connector streams notification metrics via the OpenTelemetry Protocol (OTLP) over HTTP in near real-time — with latency under 1 minute. It covers three key areas of your notification pipeline:
API Requests
Track every API call hitting SuprSend — success/failure counts, error breakdowns, and request volume over time.
Workflow Executions
Monitor workflow performance, catch execution errors early, and identify top failing workflows.
Messages
Follow the full message lifecycle — triggered, delivered, seen, clicked — with delivery errors by vendor and channel.
Use it to connect SuprSend to any platform that accepts OTLP, including Grafana Cloud, Prometheus, Honeycomb, Dynatrace, or your own self-hosted OTel Collector.
Connecting to Datadog or New Relic? Use our dedicated connectors with pre-built dashboard starter kits — Datadog connector · New Relic connector
Enterprise plan feature. The SuprSend OTel connector is only available on our Enterprise plan.
SuprSend exports suprsend.* metrics via OTLP over HTTP. You provide your OTLP endpoint and authentication headers, choose which events to sync, and SuprSend streams them in near real-time — with latency under 1 minute.Once connected you can build custom dashboards, set up alerts for delivery failures or API errors, slice by any dimension (workspace, tenant, workflow, channel, vendor, template), and correlate notification health with your infrastructure and APM data.All metrics are tagged by workspace, tenant, workflow, category, channel, vendor, template, node, and error details. See Reported metrics for the full list.
Please refer to your observability platform’s pricing agreement for information on how custom metrics ingested via OTLP are priced.
SuprSend passes authentication credentials as HTTP headers. The header format depends on your platform:
Auth type
Header key
Header value
Used by
Bearer token
Authorization
Bearer <your-api-key>
Datadog, Honeycomb, Dynatrace
Basic auth
Authorization
Basic <base64(username:password)>
Grafana Cloud
Custom header
varies
varies
Self-hosted collectors
We recommend creating a dedicated API key or token specifically for SuprSend so you can rotate or revoke it independently without affecting other integrations.
SuprSend streams the following suprsend.* counter metrics. All counters are monotonically increasing and represent cumulative counts from the time the connector is enabled.
Track the volume and health of every API call made to SuprSend.
Metric
Description
suprsend.api_request.total
Total number of API requests received by SuprSend. Use the status tag to break down by outcome — sent, in_progress, success, failed, or partial_failure.
suprsend.api_request.errors
API requests that failed to process due to an error. Group by api_type to identify which endpoint is failing, and by error_severity to prioritize investigation.
Monitor how your workflows and broadcasts are performing and quickly spot execution failures.
Metric
Description
suprsend.workflow_execution.total
Total number of workflow executions started. Workflow executions are counted per-recipient. Use workflow_slug and category tags to drill down into specific workflows.
suprsend.workflow_execution.errors
Workflow executions that failed to process due to an error.
suprsend.broadcast_execution.errors
Broadcast executions that failed to process due to an error.
Tags on Workflow Execution metrics
Tag
Description
Example values
workflow_slug
Slug of the workflow that was executed
welcome-flow, order-confirmation
category
Notification category of the workflow
transactional, promotional
workspace_slug
Slug of the SuprSend workspace
my-workspace
workspace_key
Identifier of the SuprSend workspace (environment)
your_workspace_key
tenant_id
Tenant ID if the workflow is scoped to a tenant
tenant_abc
error_severity
Severity level of the error (on error metrics only)
All metrics are scoped to the SuprSend environment (e.g. production, staging) via the workspace_key tag.
For delivery, seen, and click metrics to be populated for Email, SMS, and WhatsApp, configure https://hub.suprsend.com/webhook/* as a callback URL in your vendor dashboard. See the vendor integration docs for per-vendor instructions.
