RunReveal destination

The runreveal destination sends events to RunReveal via your webhook URL. Events are batched and flushed on a configurable interval for efficient delivery.

Configuration

{
  "destinations": {
    "runreveal": {
      "type": "runreveal",
      "webhookURL": "$WEBHOOK_URL"
    }
  }
}

Options

Option	Type	Default	Description
`webhookURL`	string	required	RunReveal webhook URL. Supports environment variable substitution with `$VAR`.
`batchSize`	int	`100`	Number of events per batch
`flushFreq`	duration	`"15s"`	Time between batch flushes
`version`	int	`0`	Wire format version (`0` = legacy, `1` = native)

Getting your webhook URL

Go to your RunReveal dashboard
Navigate to Sources and create a Reveald source
Copy the generated webhook URL

The URL looks like: https://api.runreveal.com/sources/reveald/webhook/<id>

Store your webhook URL in an environment variable rather than directly in the config file. See Configuration.

Wire format versions

Legacy format (v0, default)

The default format sends events with base64-encoded rawLog and a contentType field. This is compatible with all RunReveal versions.

Native format (v1)

The native format sends rawLog as raw JSON with structured fields like actor, service, and tags. Enable it with "version": 1:

{
  "destinations": {
    "runreveal": {
      "type": "runreveal",
      "webhookURL": "$WEBHOOK_URL",
      "version": 1
    }
  }
}

Tuning

For high-volume deployments, increase the batch size and flush interval:

{
  "destinations": {
    "runreveal": {
      "type": "runreveal",
      "webhookURL": "$WEBHOOK_URL",
      "batchSize": 500,
      "flushFreq": "10s"
    }
  }
}

Larger batches reduce HTTP overhead but increase memory usage and latency before events appear in RunReveal.

On this page