EvoHub

FortiGate alerts, routed to the right on-call engineer

Receive FortiGate (FortiOS) event logs via an automation stitch Webhook action. EvoHub turns each FortiGate alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.

How the FortiGate integration works

  1. Create a FortiGate integration in EvoHub On-Call and pick the escalation policy it should notify.
  2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into FortiGate using the steps below.
  3. Each FortiGate alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
  4. No — log events carry no recovery; resolve in EvoHub.

Set up FortiGate

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

# 1. Security Fabric → Automation → Action → Create → Webhook
#    (or the CLI below)
Protocol: HTTPS
URL: <your EvoHub integration URL>
Method: POST
HTTP body: %%log%%
#    %%log%% is the FortiOS log line (date=… logid="…" msg="…"),
#    which EvoHub reads as it is.
#    Optionally keep the key out of the URL: drop ?key=… and add
#    the HTTP header  Authorization = Bearer <your integration key>

config system automation-action
    edit "evohub"
        set action-type webhook
        set protocol https
        set method post
        set uri "<the URL above, without https://>"
        set port 443
        set http-body "%%log%%"
        config http-headers
            edit 1
                set key "Authorization"
                set value "Bearer <your integration key>"
            next
        end
    next
end
#    (With the header, the uri needs no ?key=…)

# 2. Automation → Trigger → FortiOS Event Log, and pick the
#    log IDs that should page (e.g. Admin login failed, HA
#    failover, VPN tunnel down). Avoid traffic logs — every
#    matching log is one delivery.

# 3. Automation → Stitch: that trigger → the "evohub" action.

# One EvoHub alert per FortiGate and log ID; repeats retrigger
# it. emergency / alert / critical → critical, error → high,
# warning → medium, notice → low, information → info.
# FortiGate sends no recovery — resolve in EvoHub.

FortiGate + EvoHub — FAQ

How do I connect FortiGate to EvoHub?

In EvoHub, go to On-Call → Integrations, add FortiGate, and choose an escalation policy. Then configure FortiGate with the integration URL EvoHub shows you — the exact steps are on this page.

Do FortiGate alerts resolve automatically in EvoHub?

No — log events carry no recovery; resolve in EvoHub.

How is the FortiGate integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.

Start free — 200 EvoHub tokens every month. See pricing.

Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.