# Filebeat -\> logstash -\> SIEM

**URL:** <https://discuss.elastic.co/t/filebeat-logstash-siem/187260>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 25, 2019, 8:24am UTC](https://discuss.elastic.co/t/filebeat-logstash-siem/187260 "2019-06-25T08:24:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vladx](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vladx/32/48089_2.png) [@Vladx](https://discuss.elastic.co/u/Vladx)\
**Post date:** [June 25, 2019, 8:24am UTC](https://discuss.elastic.co/t/filebeat-logstash-siem/187260/1 "2019-06-25T08:24:05Z")

</div>

Hi,

I'm trying to put together a pilot with ELK plus Qradar. The ELK part works like a charm, but I have some issues on Qradar side. This is heavily relies on proper syslog fields, but unfortunately when I forward logs received on beats input using logstash, important fields (like $srchost, $timestamp) are missing.

I thought, it is no problem, I can put together a proper syslog message using the mutate filter, but it seems I cannot access fields in beats. Any idea for a proper mutate filter?

This is what I've tried

> filter {  
> mutate {  
> ;; add\_field =\> ["syslogmsg", "\<%{priority}\>%{timestamp} %{logsource} %{program}[%{pid}]: %{message}"]  
> add\_field =\> ["syslogmsg", "\<%{syslog.priority}\>%{message}"]  
> }  
> }

Thanks  
L:

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 23, 2019, 8:26am UTC](https://discuss.elastic.co/t/filebeat-logstash-siem/187260/2 "2019-07-23T08:26:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.