Webhooks

Linknesis can send test lifecycle events to external HTTP endpoints.

Queued delivery

Instead of sending HTTP requests directly, the Core writes events to a MongoDB queue. A separate linknesis-webhook-sender container polls the queue and dispatches events one-by-one via curl. This decouples the Core from slow or unreachable endpoints.

Event types

  • test_complete — summary when a test finishes
  • test_error — when a test fails
  • test_interval — every result interval (when enabled)
  • threshold_alert — when configured thresholds are breached

Modes

  • report_on_end — send a summary on completion/failure
  • all_events — queue every test result interval
  • thresholds — send alerts only when limits are breached

Per-test webhooks

Each test can define its own webhook configuration in addition to the global one. Per-test events include the test-specific URL, secret, timeout, and rotation policy.

© Linknesis. Documentation for the Linknesis network monitoring platform.