Skip to content
AirgateDocumentation

Splunk

Send Airgate events to Splunk through the HTTP Event Collector, either as a continuous log export or as individual events from an access rule.

Airgate sends data to Splunk through the HTTP Event Collector (HEC) in two ways. This page explains both and when to use each.

Status: Available. Event export to Splunk HEC (Settings › Log export) and the Splunk HEC context server for HTTP actions. A Splunk app with dashboards for Airgate data is Planned (see Planned integrations).

Way What it sends Configured in
Log export, transport Splunk HEC Every event of the selected topics (sign-ins, sessions, TACACS+, guests, certificates, alerts, audit), batched Settings › Log export
Splunk HEC context server and action One event per run of an access rule, with fields you choose Settings › Webhooks

For a SIEM feed, use the log export. Use the HTTP action only to mark specific policy outcomes.

  • Splunk Enterprise or Splunk Cloud with HEC enabled, and a HEC token allowed to write to your index.
  • The HEC endpoint (for example https://splunk.contoso.com:8088) reachable from Airgate over HTTPS.
  • An Airgate administrator with admin:write.
  1. Open Settings › Log export and select Add target.
  2. Transport: Splunk HEC. Enter HEC URL (https://splunk.contoso.com:8088; /services/collector/event is appended unless the URL already contains /services/collector), HEC token, and optionally Index, Sourcetype and Source.
  3. Format: JSON (or CEF / LEEF).
  4. Save.

Airgate sends batches of up to 100 events (or every second), with 3 attempts per batch. The full setup, topics and troubleshooting are in Export events to syslog and SIEM.

Option B: Send an event from an access rule

Section titled “Option B: Send an event from an access rule”
  1. Open Settings › Webhooks, select Context servers and Add context server. Choose Splunk HEC:

    Field Value
    Name Splunk
    Base URL https://splunk.contoso.com:8088 (required)
    Authentication API key (default): sent as Authorization: Splunk <token>. Bearer token is also accepted.
    API key the HEC token (stored encrypted)
  2. Save, then select Test connection. Airgate calls GET /services/collector/health; a success shows “Splunk HEC healthy”.

  3. Select Context actions › Add action, pick the preset Splunk HEC event and the server:

    Field Value
    Method, URL POST /services/collector/event
    Content type application/json
    Body {"sourcetype":"nac:nac:action","event":{"username":"%{Authentication:Username}","mac":"%{Connection:Client-Mac-Address}","role":"%{Tips:Role}","posture":"%{Tips:Posture}"}}

    Change sourcetype to your naming, and add "index": "network" if the token has no default index.

  4. Save, then Test › Send request.

  5. Create an HTTP enforcement profile for the action and attach it to a rule through the API; see Webhooks and HTTP actions, Step 3.

  • In Splunk: index=<your index> sourcetype=<your sourcetype> returns events.
  • Log export: on Settings › Log export the target’s Status is Posting or Sending, and Sent · drop · err shows messages sent.
  • HTTP action: Settings › Webhooks › Execution log shows HTTP 200.
Symptom Cause Fix
HEC HTTP 403 Wrong token, or the token cannot write to the index. Check the token and its allowed indexes.
Test: HEC health returned HTTP 503 HEC is disabled or overloaded. Enable HEC under Settings › Data inputs › HTTP Event Collector › Global Settings in Splunk.
TLS error Splunk’s certificate is not trusted. Add its CA under Trusted CA certificate(s).
Events arrive but fields are not extracted The sourcetype has no JSON extraction. Use _json-based sourcetypes or KV_MODE = json.