---
description: >-
  Custom VRL scripts per source can be enabled for advanced customization and
  filtering options.
---

# Custom VRL Scripts

Enable custom VRL in the advanced options by setting source.custom\_vrl to True.

<figure><img src="https://1537627201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIeQBo8pSOQxxjibSlMb4%2Fuploads%2FxAooxp4yKhepHuqF7XDz%2Fcustom_vrl_advanced_settings.png?alt=media&#x26;token=9b9a4c92-2cd4-43b4-88e9-75a4c67be064" alt=""><figcaption></figcaption></figure>

This will provide the following files on the collector which can have custom VRL added to them. These files are not removed or overwritten if _**source.custom\_vrl**_ is disabled or re-enabled:

* /etc/collector/vrl/event\_beats.vrl
* /etc/collector/vrl/event\_hypersec.vrl
* /etc/collector/vrl/event\_netflow.vrl
* /etc/collector/vrl/event\_nxlog.vrl
* /etc/collector/vrl/event\_syslog.vrl

The VRL is required to be valid, and if incorrect VRL is inserted the vector instance may fail. The Administrator adding the VRL must ensure it is valid and correct.

Once edited, the Administrator must restart vector to effect the changes in the custom scripts:

`systemctl restart vector`
