# Can I turn the path (or parts of it) into a variable?

**URL:** <https://discuss.elastic.co/t/can-i-turn-the-path-or-parts-of-it-into-a-variable/87129>\
**Category:** Beats\
**Created:** [May 25, 2017, 1:19pm UTC](https://discuss.elastic.co/t/can-i-turn-the-path-or-parts-of-it-into-a-variable/87129 "2017-05-25T13:19:03Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jclose](https://avatars.discourse-cdn.com/v4/letter/j/df705f/32.png) [@jclose](https://discuss.elastic.co/u/jclose)\
**Post date:** [May 26, 2017, 12:16pm UTC](https://discuss.elastic.co/t/can-i-turn-the-path-or-parts-of-it-into-a-variable/87129/3 "2017-05-26T12:16:54Z")

</div>

Not really, as I was trying to use it as a workaround to the issue I posted [here](https://discuss.elastic.co/t/logstash-config-for-using-filebeat-auditd-module/87033). Right now, the only way I've gotten the auditd module to work is via the Pipeline used by Filebeat. I tried to force Logstash to use the same pipeline, and it didn't work

My thinking was, since Logstash wasn't working for me, I can send stuff straight to file in Logstash (via file output, or I could just send it to the syslog process on the box, which is listening).

Then, I could point Filebeat to those files and ship, defining the pipeline. It was really an attempt at a workaround of that other issue. But it would still be handy to have.

---

_[View the full topic](https://discuss.elastic.co/t/can-i-turn-the-path-or-parts-of-it-into-a-variable/87129)._