Extending VectorStep

VectorStep is designed to be extended through configuration rather than by changing the software. Adding a library step is the one extension point available without engine source access; new source parsers and executors are engine-source changes, documented internally for anyone who does have that access.

Adding a library step

1. Create ~/.vectorstep/steps/<your-step-name>.yaml with at minimum name, executor, and executor_config.agent
2. Run POST /reload (or send SIGHUP) — the step will appear in /ui/steps immediately
3. Reference it in any pipeline with - use: <your-step-name>

~/.vectorstep/steps/ is an ordinary host directory — steps are personal to your deployment. The installer seeds it with starter definitions to copy and adapt, or write your own. See ~/.vectorstep/pipelines/alert-triage-investigation-using-steps.yaml for a worked example of a pipeline that uses library steps.