Integration · APM & alerting
Webhook (generic)
HMAC-SHA256 signature, retry 30s/2m/10m.
What gets collected
A JSON POST with an X-Unimoni-Signature signature and a timestamp. The receiver must verify the signature and timestamp (±5min anti-replay).
Requirements
- ✓HTTPS endpoint
- ✓HMAC-SHA256 signing secret
- ✓timestamp verification (±5min)
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
webhook.deliveredwebhook.retrieswebhook.signature.verifiedSetup steps
- 1Endpoint URL
- 2Generate a signing secret in the cabinet
- 3Verify HMAC + timestamp on your side
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Webhook (generic)
Frequently asked questions
- What does Unimoni collect from Webhook (generic)?
- HMAC-SHA256 signature, retry 30s/2m/10m. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Webhook (generic) and everything else in one place.
- How long does it take to connect Webhook (generic)?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Webhook (generic) integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Webhook (generic) monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.