WASM Transform
The Vector wasm
transform
process events using the WASM virtual machine,
allowing you to process Vector events with Typescript, Ruby, Java, and
more.
Configuration
- Common
- Advanced
- vector.toml
- vector.yaml
- vector.json
[transforms.my_transform_id]type = "wasm" # requiredinputs = ["my-source-or-transform-id"] # requiredartifact_cache = "/etc/vector/artifacts" # requiredmodule = "./modules/example.wasm" # required
- requiredstring
artifact_cache
The directory where Vector should store the artifact it builds of this WASM module. Typically, all WASM modules share this.
- View examples
- optionaluint
heap_max_size
The maximum size of the heap of this module, in bytes. (This includes the module itself, default is 10 MB.)
- Default:
10485760
(bytes)
- Default:
- requiredstring
module
The file path of the
.wasm
or.wat
module.- View examples
Telemetry
This component provides the following metrics that can be retrieved through
the internal_metrics
source. See the
metrics section in the
monitoring page for more info.
- counter
processed_events_total
The total number of events processed by this component. This metric includes the following tags:
component_kind
- The Vector component kind.component_name
- The Vector component ID.component_type
- The Vector component type.file
- The file that produced the errorinstance
- The Vector instance identified by host and port.job
- The name of the job producing Vector metrics.
- counter
processed_bytes_total
The total number of bytes processed by the component. This metric includes the following tags:
component_kind
- The Vector component kind.component_name
- The Vector component ID.component_type
- The Vector component type.instance
- The Vector instance identified by host and port.job
- The name of the job producing Vector metrics.