The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
Add Splunk HEC forward GitHub Actions reference workflow.
Ayush761423d5e1c5e213
diff --git a/cli/beacon/README.md b/cli/beacon/README.mdindex 4dc0b8f0..7fca825c 100644--- a/cli/beacon/README.md+++ b/cli/beacon/README.md@@ -371,7 +371,8 @@ See [`examples/github-actions/claude-code-telemetry.yml`](../../examples/github-[`examples/github-actions/claude-security-review-session.yml`](../../examples/github-actions/claude-security-review-session.yml),[`examples/github-actions/codex-action-session.yml`](../../examples/github-actions/codex-action-session.yml),[`examples/github-actions/s3-upload-telemetry.yml`](../../examples/github-actions/s3-upload-telemetry.yml),-and [`examples/github-actions/gcs-upload-telemetry.yml`](../../examples/github-actions/gcs-upload-telemetry.yml)+[`examples/github-actions/gcs-upload-telemetry.yml`](../../examples/github-actions/gcs-upload-telemetry.yml),+and [`examples/github-actions/splunk-forward-telemetry.yml`](../../examples/github-actions/splunk-forward-telemetry.yml)for complete reference workflows.## Wazuhdiff --git a/docs/log-forwarding/ci-telemetry-exports.mdx b/docs/log-forwarding/ci-telemetry-exports.mdxindex 8a1a531c..759ecf2f 100644--- a/docs/log-forwarding/ci-telemetry-exports.mdx+++ b/docs/log-forwarding/ci-telemetry-exports.mdx@@ -72,6 +72,36 @@ beacon ci exec --upload s3 --upload gcs -- claude --print "Review this repositorS3 upload uses `aws s3 cp` and the standard AWS credential provider chain. GCS upload uses `gcloud storage cp` when available, falling back to `gsutil cp`.+### GitHub Actions SIEM Forwarding++Set the Splunk or Falcon ingest token at the job or workflow level from a secret, then pass `forward` and `forward-endpoint` to the Agent Beacon action:++```yaml+jobs:+ claude-telemetry:+ runs-on: ubuntu-latest+ env:+ BEACON_CI_SPLUNK_HEC_TOKEN: ${{ secrets.SPLUNK_HEC_TOKEN }}+ steps:+ - uses: actions/checkout@v4++ - name: Run Claude with Beacon telemetry+ uses: asymptote-labs/[email protected]+ env:+ ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}+ with:+ command: claude --print "Review this pull request"+ forward: splunk+ forward-endpoint: https://splunk.example:8088/services/collector+ upload-artifact: "true"+```++See the sample workflow:++- [Splunk forward telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/splunk-forward-telemetry.yml)++For Falcon LogScale HEC, set `BEACON_CI_FALCON_HEC_TOKEN` and use `forward: falcon`.+### GitHub Actions Object StorageConfigure cloud credentials at the job level, then pass the upload destination to the Agent Beacon action:diff --git a/examples/github-actions/claude-code-telemetry.yml b/examples/github-actions/claude-code-telemetry.ymlindex 4ca99ac8..fd551596 100644--- a/examples/github-actions/claude-code-telemetry.yml+++ b/examples/github-actions/claude-code-telemetry.yml@@ -19,7 +19,6 @@ jobs:# exposing secrets to the Claude child process. Omit this block if you only# upload the default GitHub artifact.env:- BEACON_CI_SPLUNK_HEC_TOKEN: ${{ secrets.SPLUNK_HEC_TOKEN }}BEACON_CI_S3_BUCKET: ${{ vars.BEACON_CI_S3_BUCKET }}BEACON_CI_S3_PREFIX: github-actionssteps:@@ -44,8 +43,9 @@ jobs:command: claude --print "Summarize the changes in this pull request"# Optional: forward to a customer-managed SIEM before teardown.# Requires a Beacon release that includes ci exec --forward.- forward: splunk- forward-endpoint: https://splunk.example:8088/services/collector+ # See examples/github-actions/splunk-forward-telemetry.yml.+ # forward: splunk+ # forward-endpoint: https://splunk.example:8088/services/collector# Optional: upload the completed runtime JSONL to object storage.# Supported values: s3, gcs, or s3,gcs.# upload: s3diff --git a/examples/github-actions/splunk-forward-telemetry.yml b/examples/github-actions/splunk-forward-telemetry.ymlnew file mode 100644index 00000000..1523f83d--- /dev/null+++ b/examples/github-actions/splunk-forward-telemetry.yml@@ -0,0 +1,38 @@+# Reference workflow for testing Agent Beacon CI telemetry with direct Splunk+# HEC forwarding. Copy this file to .github/workflows/ in a test repository+# and update the Splunk endpoint, secret names, and action ref.+#+# This file lives under examples/ (not .github/workflows/) so it is a reference+# only and does not run in this repository.+# Replace <tag> with the Beacon release tag you want to run (v0.0.39 or newer).++name: Test Agent Beacon Splunk forward++on:+ workflow_dispatch:++permissions:+ contents: read++jobs:+ beacon-splunk-forward:+ runs-on: ubuntu-latest+ # Keep the Splunk token at the job level so Beacon can forward events+ # without exposing the secret to the Claude child process.+ env:+ BEACON_CI_SPLUNK_HEC_TOKEN: ${{ secrets.SPLUNK_HEC_TOKEN }}+ steps:+ - uses: actions/checkout@v4++ - name: Install Claude Code+ run: npm install -g @anthropic-ai/claude-code++ - name: Run Agent Beacon with Splunk forwarding+ uses: asymptote-labs/agent-beacon@<tag>+ env:+ ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}+ with:+ command: claude --print "Say hello from Agent Beacon CI telemetry"+ forward: splunk+ forward-endpoint: https://splunk.example:8088/services/collector+ upload-artifact: "true"