# Parsing Clamscan logs when redirecting logs to Kibana using Filebeat

**URL:** <https://discuss.elastic.co/t/parsing-clamscan-logs-when-redirecting-logs-to-kibana-using-filebeat/356202>\
**Category:** Kibana\
**Created:** [March 26, 2024, 6:30pm UTC](https://discuss.elastic.co/t/parsing-clamscan-logs-when-redirecting-logs-to-kibana-using-filebeat/356202 "2024-03-26T18:30:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cexico](https://avatars.discourse-cdn.com/v4/letter/c/848f3c/32.png) [@Cexico](https://discuss.elastic.co/u/Cexico)\
**Post date:** [March 26, 2024, 6:30pm UTC](https://discuss.elastic.co/t/parsing-clamscan-logs-when-redirecting-logs-to-kibana-using-filebeat/356202/1 "2024-03-26T18:30:28Z")

</div>

what should I do to understand the clamscan result that I do in the terminal in kibana logs normally? how should I do the parsing part, write a grok filter?

---

<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:** [April 23, 2024, 6:30pm UTC](https://discuss.elastic.co/t/parsing-clamscan-logs-when-redirecting-logs-to-kibana-using-filebeat/356202/2 "2024-04-23T18:30:58Z")

</div>

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