# Pipelines for each device source

**URL:** <https://discuss.elastic.co/t/pipelines-for-each-device-source/296962>\
**Category:** Elasticsearch\
**Created:** [February 11, 2022, 10:24am UTC](https://discuss.elastic.co/t/pipelines-for-each-device-source/296962 "2022-02-11T10:24:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jokem48](https://avatars.discourse-cdn.com/v4/letter/j/3ec8ea/32.png) [@jokem48](https://discuss.elastic.co/u/jokem48)\
**Post date:** [February 11, 2022, 10:24am UTC](https://discuss.elastic.co/t/pipelines-for-each-device-source/296962/1 "2022-02-11T10:24:01Z")

</div>

Hi, new to the ELK setup. We are exploring to use ELK as our SIEM. Right now we have a log forwarder collecting syslog from various network sources, like cisco, fortinet and even juniper /f5?

In order to break down those logs in the Kibana side, we will need to 1 pipeline for each individual source? Is there any community info that guide us how to create individual pipelines pertaining to different log sources?

---

<div class="post-metadata">

**Author:** ![Tomo\_M](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@Tomo\_M](https://discuss.elastic.co/u/Tomo_M)\
**Post date:** [February 11, 2022, 10:47am UTC](https://discuss.elastic.co/t/pipelines-for-each-device-source/296962/2 "2022-02-11T10:47:20Z")

</div>

Elastic integrations looks good for you.

> **[Elastic integrations | Elastic](https://www.elastic.co/jp/integrations/data-integrations)**

---

<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:** [March 11, 2022, 10:48am UTC](https://discuss.elastic.co/t/pipelines-for-each-device-source/296962/3 "2022-03-11T10:48:06Z")

</div>

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