Skip to main content
Garnet surfaces assertion results through two channels: GitHub Actions Job Summaries (automatic) and webhooks (configured in Settings → Alerting).

GitHub Actions Job Summary

When the Garnet action runs in a workflow, it generates a Runtime Report in the Job Summary — visible directly in the GitHub UI. GitHub Actions Job Summary showing Garnet Runtime Report with failed assertion The report includes:
  • Workload Summary — Workflow, repository, branch, commit, and trigger actor
  • Network Egress Summary — Every destination contacted, with the full process tree and a green/red status indicator
  • Network Telemetry Summary — Aggregate stats (unique domains, connections, flows)
  • Assertions — Pass/fail result for each check (e.g., no_bad_egress_domain → fail)
Job Summaries appear for all workflow triggers (push, pull_request, workflow_dispatch, etc.) — no extra configuration needed.

Webhooks

Settings Alerting tab with webhook configuration
Go to SettingsAlerting to configure webhook endpoints. Garnet supports Slack webhooks and custom HTTP endpoints.

Adding a Slack webhook

  1. Create a Slack Incoming Webhook — create a Slack app, enable Incoming Webhooks, add to your channel, copy the URL.
  2. In Garnet, go to SettingsAlertingAdd Webhook and paste the URL.

Settings tabs

TabWhat it contains
SetupOnboarding guide and runtime agent installation instructions
API TokensCreate, view, copy, and delete tokens for runtime agent authentication
AlertingConfigure webhook endpoints for Slack and custom notifications
UsagePlatform usage metrics
Store API tokens securely. Use repository secrets or environment secrets — never commit tokens in code or logs.