# ECS & Palo Alto Logs

**URL:** <https://discuss.elastic.co/t/ecs-palo-alto-logs/167542>\
**Category:** Logstash\
**Tags:** ecs-elastic-common-schema\
**Created:** [February 7, 2019, 10:05pm UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542 "2019-02-07T22:05:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidhowell.tx](https://avatars.discourse-cdn.com/v4/letter/d/6de8d8/32.png) [@davidhowell.tx](https://discuss.elastic.co/u/davidhowell.tx)\
**Post date:** [February 7, 2019, 10:05pm UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542/1 "2019-02-07T22:05:53Z")

</div>

Hello. I've seen some logstash pipelines for parsing Palo Alto logs by using CSV plugin. I'm curious if anyone has taken this a step further and aligned the fields with the Elastic Common Schema. I am working on doing this, and some of the field mappings seem nebulous.

I currently have some of the log types mapped with some additional fields not defined in ECS framework, I am just hoping to find someone else on this path with which I can compare notes.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [February 15, 2019, 1:09pm UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542/2 "2019-02-15T13:09:49Z")

</div>

There has been some discussion at:

> <https://github.com/elastic/beats/issues/9199>

---

<div class="post-metadata">

**Author:** ![davidhowell.tx](https://avatars.discourse-cdn.com/v4/letter/d/6de8d8/32.png) [@davidhowell.tx](https://discuss.elastic.co/u/davidhowell.tx)\
**Post date:** [February 26, 2019, 9:55pm UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542/3 "2019-02-26T21:55:05Z")

</div>

Andrew,  
Do you think discuss is a better place to have a discussion on the topic, or should I talk about it on the Github issue?  
I'd also be interested in just talking about mappings from log field to ECS field, as I'm probably not going to send to a central syslog server with filebeat installed, rather sending from Palo Alto using the syslog forwarder to a load balancer and straight into Logstash where I map the fields myself.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [February 27, 2019, 3:00am UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542/4 "2019-02-27T03:00:22Z")

</div>

I'm good with using that issue to generally discuss the mappings. I haven't really taken a close look at the fields yet, but Mike has. I'll ask him to make those spreadsheets publicly readable so you can see the mappings he started.

---

<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 27, 2019, 3:00am UTC](https://discuss.elastic.co/t/ecs-palo-alto-logs/167542/5 "2019-03-27T03:00:24Z")

</div>

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