# Parse custom logs in Elastic cloud
**URL:** https://discuss.elastic.co/t/parse-custom-logs-in-elastic-cloud/219044
**Category:** Beats
**Tags:** filebeat
**Created:** [February 12, 2020, 4:36pm UTC](https://discuss.elastic.co/t/parse-custom-logs-in-elastic-cloud/219044 "2020-02-12T16:36:56Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@arkaitzgarro](https://discuss.elastic.co/u/arkaitzgarro)
#### Post date: [February 12, 2020, 4:36pm UTC](https://discuss.elastic.co/t/parse-custom-logs-in-elastic-cloud/219044/1 "2020-02-12T16:36:57Z")
I'm sending custom logs with `filebeat` to Elasticsearch, but I would like to be able to parse them and extract some information. I see the document on Kibana, but the message is the whole log entry:
[2020-02-12 16:26:23] env.ERROR: Command "xxx" is not defined. {"exception":"[object] (Symfony\Component\Console\Exception\CommandNotFoundException(code: 0): Command "xxx" is not defined. at /path/vendor/symfony/console/Application.php:642)"}
How can I parse those messages? I tried to create a pipeline, but I don't what values should provide for input/output blocks.
Thanks in advance.
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [February 24, 2020, 2:46pm UTC](https://discuss.elastic.co/t/parse-custom-logs-in-elastic-cloud/219044/2 "2020-02-24T14:46:37Z")
Hi @arkaitzgarro,
did you try to use the [dissect processor](https://www.elastic.co/guide/en/elasticsearch/reference/current/dissect-processor.html) in your ingest pipeline?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 23, 2020, 2:46pm UTC](https://discuss.elastic.co/t/parse-custom-logs-in-elastic-cloud/219044/3 "2020-03-23T14:46:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.