# Handling multiple logstream formats with Functionbeat **URL:** \ **Category:** Beats\ **Tags:** functionbeat\ **Created:** [January 14, 2021, 9:00pm UTC](https://discuss.elastic.co/t/handling-multiple-logstream-formats-with-functionbeat/261181 "2021-01-14T21:00:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Karl\_Falconer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karl_falconer/32/74795_2.png) [@Karl\_Falconer](https://discuss.elastic.co/u/Karl_Falconer)\ **Post date:** [January 14, 2021, 9:00pm UTC](https://discuss.elastic.co/t/handling-multiple-logstream-formats-with-functionbeat/261181/1 "2021-01-14T21:00:20Z")
Hi, I have a working function beat sending logs from Cloudwatch containing mysql slow query data ES and am able to view the log data in Kibana. I am trying to understand a few things regarding various log types. 1. What is the best practice for dealing with multiple log groups having different formats. Ex: mysql (RDS) slow query, error, AWS ELB, S3, etc. Do we have one function with multiple streams, or a function per stream? 2. Related to above, how do we then handling the different parsing requirements for each log group. Is this a general Beats issue where we'd setup a single pipeline, and then have multiple processesors for each expected log type? 3. Am I correct in assuming that even though Kibana and Filebeats has support for Mysql, that because we are getting these logs from functionbeat, we can't use the pre-built dashboards? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 11, 2021, 11:00pm UTC](https://discuss.elastic.co/t/handling-multiple-logstream-formats-with-functionbeat/261181/2 "2021-02-11T23:00:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.