Set up Splunk

Lidar still detects and triages inside Authdog. This channel copies the same events to the HEC endpoint you already watch. Configuration belongs to one environment.

Create the channel

In the Authdog console:

1. Select the project and environment.
2. Open Notifications > Channels.
3. Select Add Channel.
4. Set Channel Name and Channel Type to Splunk.
5. Set Collector URL to the HEC base URL, for example https://http-inputs-acme.splunkcloud.com. Authdog appends /services/collector/event.
6. Paste the HEC Token.
7. Optionally set Sourcetype (default authdog:audit), Source, and Index. Leave Index blank to use the token's default index.
8. Choose the event triggers. Leave the event list empty to drain every event. Build a narrower list from the event catalog.
9. Save, then send a test delivery.

The HEC token is stored as a secret. Later edits show it as redacted. Select Change only when you are replacing it.

What lands in Splunk

Deliveries use the HEC token, not the X-Authdog-Signature header used by generic webhooks. A 2xx from Splunk is success. Failures retry with exponential backoff, starting at 60 seconds, for at most five attempts. Inspect delivery records if a test does not appear.

This is log intake, not a Lidar detector. Signals stay in the console under Lidar.

Test it

1. Trigger a sign-in in the same environment.
2. Search the index for sourcetype authdog:audit, or the sourcetype you set.
3. Confirm a failed destination shows up in delivery records, then recovers after Splunk accepts the retry.

Repeat the channel in production with a production token. Channels do not copy between environments.

Related