Merge pull request #924 from flashcatcloud/feat/alert-batch21-test

docs: sync Kener, Coroot, Dkron, Duplicati, Ofelia, Trigger.dev, Robotalp alert pages to test

Author: ysyneu

docs.json

@@ -1705,6 +1705,9 @@
                       "zh/on-call/integration/alert-integration/alert-sources/aikido",
                       "zh/on-call/integration/alert-integration/alert-sources/cato",
                       "zh/on-call/integration/alert-integration/alert-sources/rollbar",
+                      "zh/on-call/integration/alert-integration/alert-sources/trigger-dev",
+                      "zh/on-call/integration/alert-integration/alert-sources/duplicati",
+                      "zh/on-call/integration/alert-integration/alert-sources/robotalp",
                       "zh/on-call/integration/alert-integration/alert-sources/fivetran",
                       "zh/on-call/integration/alert-integration/alert-sources/coralogix",
                       "zh/on-call/integration/alert-integration/alert-sources/uptimeobserver",
@@ -1714,6 +1717,7 @@
                       "zh/on-call/integration/alert-integration/alert-sources/honeycomb",
                       "zh/on-call/integration/alert-integration/alert-sources/mongodb-atlas",
                       "zh/on-call/integration/alert-integration/alert-sources/honeybadger",
+                      "zh/on-call/integration/alert-integration/alert-sources/ofelia",
                       "zh/on-call/integration/alert-integration/alert-sources/openobserve",
                       "zh/on-call/integration/alert-integration/alert-sources/postman",
                       "zh/on-call/integration/alert-integration/alert-sources/contrast",
@@ -1730,9 +1734,11 @@
                       "zh/on-call/integration/alert-integration/alert-sources/panther",
                       "zh/on-call/integration/alert-integration/alert-sources/axiom",
                       "zh/on-call/integration/alert-integration/alert-sources/checkmk",
+                      "zh/on-call/integration/alert-integration/alert-sources/dkron",
                       "zh/on-call/integration/alert-integration/alert-sources/auvik",
                       "zh/on-call/integration/alert-integration/alert-sources/domotz",
                       "zh/on-call/integration/alert-integration/alert-sources/ntopng",
+                      "zh/on-call/integration/alert-integration/alert-sources/kener",
                       "zh/on-call/integration/alert-integration/alert-sources/ohdear",
                       "zh/on-call/integration/alert-integration/alert-sources/dbmarlin",
                       "zh/on-call/integration/alert-integration/alert-sources/cloudamqp",
@@ -1864,6 +1870,7 @@
                       "zh/on-call/integration/alert-integration/alert-sources/monitive",
                       "zh/on-call/integration/alert-integration/alert-sources/hosted-graphite",
                       "zh/on-call/integration/alert-integration/alert-sources/netbeez",
+                      "zh/on-call/integration/alert-integration/alert-sources/coroot",
                       "zh/on-call/integration/alert-integration/alert-sources/apimetrics",
                       "zh/on-call/integration/alert-integration/alert-sources/gatus",
                       "zh/on-call/integration/alert-integration/alert-sources/metoro",
@@ -3311,6 +3318,9 @@
                       "en/on-call/integration/alert-integration/alert-sources/aikido",
                       "en/on-call/integration/alert-integration/alert-sources/cato",
                       "en/on-call/integration/alert-integration/alert-sources/rollbar",
+                      "en/on-call/integration/alert-integration/alert-sources/trigger-dev",
+                      "en/on-call/integration/alert-integration/alert-sources/duplicati",
+                      "en/on-call/integration/alert-integration/alert-sources/robotalp",
                       "en/on-call/integration/alert-integration/alert-sources/fivetran",
                       "en/on-call/integration/alert-integration/alert-sources/coralogix",
                       "en/on-call/integration/alert-integration/alert-sources/uptimeobserver",
@@ -3320,6 +3330,7 @@
                       "en/on-call/integration/alert-integration/alert-sources/honeycomb",
                       "en/on-call/integration/alert-integration/alert-sources/mongodb-atlas",
                       "en/on-call/integration/alert-integration/alert-sources/honeybadger",
+                      "en/on-call/integration/alert-integration/alert-sources/ofelia",
                       "en/on-call/integration/alert-integration/alert-sources/openobserve",
                       "en/on-call/integration/alert-integration/alert-sources/postman",
                       "en/on-call/integration/alert-integration/alert-sources/contrast",
@@ -3336,9 +3347,11 @@
                       "en/on-call/integration/alert-integration/alert-sources/panther",
                       "en/on-call/integration/alert-integration/alert-sources/axiom",
                       "en/on-call/integration/alert-integration/alert-sources/checkmk",
+                      "en/on-call/integration/alert-integration/alert-sources/dkron",
                       "en/on-call/integration/alert-integration/alert-sources/auvik",
                       "en/on-call/integration/alert-integration/alert-sources/domotz",
                       "en/on-call/integration/alert-integration/alert-sources/ntopng",
+                      "en/on-call/integration/alert-integration/alert-sources/kener",
                       "en/on-call/integration/alert-integration/alert-sources/ohdear",
                       "en/on-call/integration/alert-integration/alert-sources/dbmarlin",
                       "en/on-call/integration/alert-integration/alert-sources/cloudamqp",
@@ -3470,6 +3483,7 @@
                       "en/on-call/integration/alert-integration/alert-sources/monitive",
                       "en/on-call/integration/alert-integration/alert-sources/hosted-graphite",
                       "en/on-call/integration/alert-integration/alert-sources/netbeez",
+                      "en/on-call/integration/alert-integration/alert-sources/coroot",
                       "en/on-call/integration/alert-integration/alert-sources/apimetrics",
                       "en/on-call/integration/alert-integration/alert-sources/gatus",
                       "en/on-call/integration/alert-integration/alert-sources/metoro",

en/on-call/integration/alert-integration/alert-sources/cfengine.mdx

@@ -59,7 +59,7 @@ The script does not parse the parameter file. It sends every `KEY='VALUE'` line
 
 <Step title="Upload the script">
 
-1. Log in to Mission Portal, click **Settings** in the top right, and open **Custom notification scripts**
+1. Log in to Mission Portal, open the user menu at the top right (Hello, username), choose **Settings**, and open **Custom notification scripts**
 2. Click **Add script**, upload `flashduty_custom_action.sh`, and enter a name (for example `Flashduty`) and a description
 3. Click **Save**
 

en/on-call/integration/alert-integration/alert-sources/coroot.mdx

@@ -0,0 +1,144 @@
+---
+title: "Coroot Alert Integration"
+description: "Sync Coroot alert and SLO incident open and resolve notifications to Flashduty On-call through a Webhook integration."
+keywords: ["alert integration", "Coroot", "Webhook", "Incident", "Alert", "observability"]
+---
+
+Sync the alerts (alerting rules) and SLO incidents of a Coroot project to Flashduty On-call through Coroot's Webhook integration. Coroot sends one notification when an alert or incident opens and one when it resolves; both map to the same Flashduty alert, which closes automatically on resolution.
+
+<div className="hide">
+
+## In Flashduty On-call
+---
+
+You can get the integration push URL in either of the following ways.
+
+### Use a dedicated integration
+
+1. In the Flashduty console, go to **Channels** and open a channel
+2. Select **Configuration** → **Integrations** → **Private integration**, then click **Add an integration**
+3. Select **Coroot** and click **Save**
+4. Open the new integration card and copy the **push URL**
+
+### Use a shared integration
+
+1. In the Flashduty console, go to **Integration Center → Alert Events**
+2. Select **Coroot** and enter an integration name
+3. Configure the default route and pick a channel; add more rules under **Routes** later
+4. Click **Save** and copy the generated **push URL**
+
+</div>
+
+## In Coroot
+---
+
+<Steps>
+<Step title="Create a Webhook integration">
+
+1. In Coroot, go to **Project Settings → Integrations** and create a **Webhook** integration
+2. Paste the full Flashduty push URL into **Webhook URL**
+3. Enable **Incidents** and **Alerts**. **Deployments** do not become alerts, so leave it off (if enabled, Flashduty receives and ignores deployment notifications)
+4. No HTTP basic authentication is needed; Coroot always sends `Content-Type: application/json`
+
+</Step>
+
+<Step title="Fill in the templates">
+
+Use Coroot's built-in `json` function in both the **Incident template** and the **Alert template**:
+
+```gotemplate
+{{ json . }}
+```
+
+<Warning>
+Keep `{{ json . }}` and do not replace it with a custom text template. Flashduty reads the alert or incident ID from the `url` field of the JSON as the Alert Key, and rejects the request when it is missing.
+</Warning>
+
+To carry fixed values such as the environment or team into Flashduty, add key-value pairs under **Custom fields** (for example `environment` = `production`). Coroot puts them at the top level of the JSON, and Flashduty turns them into labels.
+
+</Step>
+
+<Step title="Turn on notification routing">
+
+1. Go to **Project Settings → Applications** and select an application category
+2. Turn on **Webhook** for **Incidents** and **Alerts**; repeat for every category you want to cover
+
+Coroot only sends webhooks for categories that have notifications enabled.
+
+</Step>
+
+<Step title="Verify">
+
+1. Back in the Webhook integration form, click **Test**. Flashduty returns success and opens an Info alert titled `Coroot test notification`, which you close manually. Each click opens a new test alert
+2. Let an alerting rule or SLO actually fire and confirm Flashduty shows an active alert; then let it resolve and confirm the same alert closes
+
+</Step>
+</Steps>
+
+## Alert Key
+---
+
+Flashduty uses the ID carried in the `url` field of the Coroot notification as the Alert Key:
+
+| Coroot notification | Source | Alert Key |
+| :--- | :--- | :--- |
+| Alert | `alert` parameter of `url`, such as `.../alerts?alert=abc123def456` | `alert:abc123def456` |
+| Incident | `incident` parameter of `url`, such as `.../incidents?incident=x1y2z3w4` | `incident:x1y2z3w4` |
+
+Coroot generates a unique ID when it creates an alert or incident, and the open and resolve notifications use the same one. If the same rule fires again on the same application, Coroot creates a new ID, so it is a new Flashduty alert. Changes to severity, rule name, summary or the domain in `url` never change the Alert Key.
+
+## Status and severity
+---
+
+Coroot sends a notification only when an alert or incident opens or resolves; a severity change in between is not notified.
+
+| Coroot `status` | Flashduty status or severity |
+| :--- | :--- |
+| `CRITICAL` | Critical |
+| `WARNING` | Warning |
+| `INFO` | Info |
+| `OK` | Recovery |
+
+- When an alert resolves, the original severity comes from the `severity` field (`warning` or `critical`)
+- An incident notification carries only `status`, so its recovery event gets the Info severity
+- An unrecognized `status` is treated as Warning, so that Coroot is not made to pause later notifications by an error response
+
+## Labels
+---
+
+| Label | Meaning |
+| :--- | :--- |
+| `resource` | Application name |
+| `application` | The full Coroot application ID, `[cluster:]namespace:Kind:name` |
+| `namespace`, `kind` | Namespace and kind from the application ID |
+| `check` | Rule name for an alert; always `SLO` for an incident |
+| `rule_name`, `severity`, `project_name` | Rule, severity and project name of an alert |
+| `alert_id` or `incident_key` | The ID used for the Alert Key |
+| Custom fields | Custom fields configured on the integration |
+
+## Troubleshooting
+---
+
+<AccordionGroup>
+<Accordion title="Coroot logs show failed to send alert ... 400">
+Check that both templates are `{{ json . }}` and that the push URL is complete and includes `integration_key`. Flashduty returns 400 when it cannot read an ID from `url`; Coroot then keeps retrying for an hour and holds back later notifications to the same destination.
+</Accordion>
+
+<Accordion title="An alert does not recover">
+Check that neither the Alert template nor the Incident template was changed to custom text, and that the application category has Webhook enabled for both **Alerts** and **Incidents**. The resolve notification is linked to the trigger only through the ID in `url`.
+</Accordion>
+
+<Accordion title="No Alert notifications arrive">
+Coroot sends no Alert notification when the Alert template is empty, so make sure it is filled in. Also check that Webhook is enabled for **Alerts** on the category under **Project Settings → Applications**.
+</Accordion>
+
+<Accordion title="The test succeeds but real alerts do not arrive">
+The Test button sends one fixed test incident and bypasses application category routing. Check the notification settings of the category the application belongs to, and whether the alerting rule really fires.
+</Accordion>
+
+<Accordion title="Do deployment notifications become alerts?">
+No. Deployment notifications (`url` points to the application's Deployments page) are accepted and ignored by Flashduty, whatever their `status`.
+</Accordion>
+</AccordionGroup>
+
+For the field reference, see Coroot's [Webhook](https://docs.coroot.com/alerting/webhook) and [Alerts](https://docs.coroot.com/alerting/alerts) documentation.

en/on-call/integration/alert-integration/alert-sources/dkron.mdx

@@ -0,0 +1,106 @@
+---
+title: "Dkron alert integration"
+description: "Send Dkron job failure and recovery events to Flashduty On-call through a webhook notification."
+keywords: ["alert integration", "Dkron", "cron", "scheduled jobs", "webhook"]
+---
+
+Dkron can send a webhook notification after every job execution. Point it at a Flashduty Push URL and a failed execution opens an alert in Flashduty; the next successful execution of the same job recovers that alert.
+
+<div className="hide">
+
+## In Flashduty On-call
+---
+
+You can get the Push URL in either of two ways.
+
+### Use a dedicated integration
+
+1. In the Flashduty console, go to **Channels** and open a channel
+2. Go to **Settings** → **Integrations** → **Dedicated integrations** and click **Add integration**
+3. Select **Dkron** and click **Save**
+4. Open the integration card and copy the **Push URL**
+
+### Use a shared integration
+
+1. In the Flashduty console, go to **Integration Center → Alert events**
+2. Select **Dkron** and enter an integration name
+3. Configure the default route and choose a channel; you can add more rules under **Routes** after creation
+4. Click **Save** and copy the generated **Push URL**
+
+</div>
+
+## Configure Dkron
+---
+
+Dkron has no fixed webhook body. It renders the Go template you set in `webhook-payload` and posts the result. Flashduty parses only the fields the template below produces, so use it as is. The webhook is a server-wide Dkron setting that applies to every job. It is sent once per finished job execution (after retries are used up), by the leader node, for both successes and failures.
+
+<Steps>
+<Step title="Configure the webhook">
+
+Add the following to the Dkron configuration file (for example `/etc/dkron/dkron.yml`) and replace `webhook-endpoint` with the complete Flashduty Push URL:
+
+```yaml
+webhook-endpoint: "https://api.flashcat.cloud/event/push/alert/dkron?integration_key=YOUR_INTEGRATION_KEY"
+webhook-headers:
+  - "Content-Type:application/json"
+webhook-payload: '{"job_name":{{printf "%q" .JobName}},"success":{{.Success}},"node":{{printf "%q" .NodeName}},"reporting_node":{{printf "%q" .ReportingNode}},"started_at":"{{.StartTime}}","finished_at":"{{.FinishedAt}}"}'
+```
+
+You can also use the command-line flags `--webhook-endpoint`, `--webhook-headers` and `--webhook-payload`, or the environment variables `DKRON_WEBHOOK_ENDPOINT`, `DKRON_WEBHOOK_HEADERS` and `DKRON_WEBHOOK_PAYLOAD`.
+
+<Warning>
+- Keep `job_name` and `success`. Flashduty rejects a request that lacks either one.
+- Do not add `{{.Output}}` to the template. Job output can contain quotes, control characters, or sensitive data, and Dkron does not escape it for JSON, so one unescaped character invalidates the whole body.
+- `{{printf "%q" ...}}` quotes and escapes text such as the job name. Do not replace it with `"{{.JobName}}"`.
+</Warning>
+
+</Step>
+
+<Step title="Restart Dkron">
+
+Restart the Dkron servers so the configuration takes effect. In a cluster, give every server node the same configuration so notifications keep flowing after a leader change.
+
+</Step>
+
+<Step title="Verify the lifecycle">
+
+Create a job that fails, for example with the command `false`, and run it manually. Confirm a Critical alert appears in Flashduty. Then change the job to a command that succeeds and run it again, and confirm the alert recovers. Dkron has no webhook test button, so a real execution is the only way to test.
+
+</Step>
+</Steps>
+
+## Alert Key
+---
+
+Flashduty uses the job name, `job_name` (Dkron's `JobName`), as the Alert Key. The job name identifies a job in Dkron, and every execution result of that job, success or failure, carries the same name, so a failure and the success after it land on the same alert. Changes to the node, the start and end times, or the outcome do not change the Alert Key.
+
+## Status and severity
+---
+
+| Dkron execution result | Flashduty status or severity |
+| :--- | :--- |
+| `success` is `false` | Critical |
+| `success` is `true` | Recovered; original severity Critical |
+
+Dkron has no severity, so every failed job is Critical. A request whose `success` is empty or is neither `true` nor `false` is rejected, so a request with an unknown state never lands in the wrong alert lifecycle.
+
+## Alert labels
+---
+
+| Label | Source |
+| :--- | :--- |
+| `job_name`, `check`, `resource` | Job name |
+| `node` | Node that ran the job |
+| `reporting_node` | Leader node that sent the notification |
+| `started_at`, `finished_at` | Start and end time of the execution |
+
+## Troubleshooting
+---
+
+- **Flashduty receives nothing**: Dkron only logs webhook send errors and does not retry. Confirm the server can reach `api.flashcat.cloud` and that the Push URL is complete and includes `integration_key`
+- **Dkron logs `notifier: error parsing template`**: the `webhook-payload` template has a syntax error. Compare the quotes and braces with the template above
+- **Flashduty returns a parameter error**: confirm the body is valid JSON with a non-empty `job_name` and a `success` of `true` or `false`
+- **The alert does not recover**: recovery comes from the next successful execution of the same job. If the job keeps failing or runs only once, the alert stays open; turn on [auto-close](/en/on-call/channel/create-edit) in the channel as a fallback
+- **Job retries**: Dkron notifies only after retries are used up, so failures during retries do not create alerts
+
+For more settings, see [Dkron Configuration](https://dkron.io/docs/basics/configuration/).