From 4de79ece611b90a1a5d4e3d925bd260b5ff9c01a Mon Sep 17 00:00:00 2001 From: idanlodzki Date: Thu, 15 Oct 2026 18:02:44 +0300 Subject: [PATCH 1/2] docs(alerts): HTTP actions can send without waiting for a response Co-Authored-By: Claude Fable 5.1 --- opsimate-docs/docs/alerts/actions.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/opsimate-docs/docs/alerts/actions.md b/opsimate-docs/docs/alerts/actions.md index 9b0eb03..fc5ac84 100644 --- a/opsimate-docs/docs/alerts/actions.md +++ b/opsimate-docs/docs/alerts/actions.md @@ -16,7 +16,21 @@ Each action can be limited to certain alerts by name or criteria. | Slack | Webhook URL | Channel, Message template | | Teams | Webhook URL | Title template, Message template | | Jira | Base URL, Email, API token, Project key, Issue type | Summary template, Description template | -| HTTP | URL, Method | Headers, Body template | +| HTTP | URL, Method | Headers, Body template, Don't wait for a response | + +### HTTP: Don't wait for a response + +By default an HTTP action waits for the receiver's answer (up to 10 seconds) and reports its status code. Switch on **Don't wait for a response** for endpoints that answer only once their work is done, for example a job runner that keeps the connection open until the job finishes. + +With the switch on: + +- The run is reported as **sent** as soon as the request has been handed to the network. The receiver's status code is not waited for; when it arrives, it is only written to the server log. +- Anything that fails before that point still fails the run: a wrong host, a refused port, a TLS error or a connection that does not open within 10 seconds. +- **Send test** behaves the same way: it confirms the request went out, not what the receiver answered. +- OpsiMate keeps the connection open for the answer for up to 5 minutes, then drops it. +- In metrics, these runs count as `opsimate_actions_run_total{outcome="sent"}` instead of `success`. + +In the API this is `config.fireAndForget: true` on an action of type `http`. ## Variable substitution in action payloads Templates use: `{{name}}` From b029ce566de482153a3e62c92b99b66eca423580 Mon Sep 17 00:00:00 2001 From: idanlodzki Date: Thu, 15 Oct 2026 19:25:54 +0300 Subject: [PATCH 2/2] docs(alerts): no-wait HTTP actions open their own connection and don't follow redirects Co-Authored-By: Claude Fable 5.1 --- opsimate-docs/docs/alerts/actions.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/opsimate-docs/docs/alerts/actions.md b/opsimate-docs/docs/alerts/actions.md index fc5ac84..1db00ea 100644 --- a/opsimate-docs/docs/alerts/actions.md +++ b/opsimate-docs/docs/alerts/actions.md @@ -27,7 +27,8 @@ With the switch on: - The run is reported as **sent** as soon as the request has been handed to the network. The receiver's status code is not waited for; when it arrives, it is only written to the server log. - Anything that fails before that point still fails the run: a wrong host, a refused port, a TLS error or a connection that does not open within 10 seconds. - **Send test** behaves the same way: it confirms the request went out, not what the receiver answered. -- OpsiMate keeps the connection open for the answer for up to 5 minutes, then drops it. +- OpsiMate keeps the connection open for the answer for up to 5 minutes, then drops it. Each run opens its own connection. +- Redirects are not followed in this mode; a 3xx answer is logged with its `Location`. - In metrics, these runs count as `opsimate_actions_run_total{outcome="sent"}` instead of `success`. In the API this is `config.fireAndForget: true` on an action of type `http`.