# ECS for syslog: why Filebeat does not follow ECS naming convention

**URL:** <https://discuss.elastic.co/t/ecs-for-syslog-why-filebeat-does-not-follow-ecs-naming-convention/271744>\
**Category:** Logstash\
**Created:** [April 30, 2021, 7:19am UTC](https://discuss.elastic.co/t/ecs-for-syslog-why-filebeat-does-not-follow-ecs-naming-convention/271744 "2021-04-30T07:19:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jetnet](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@jetnet](https://discuss.elastic.co/u/jetnet)\
**Post date:** [April 30, 2021, 7:19am UTC](https://discuss.elastic.co/t/ecs-for-syslog-why-filebeat-does-not-follow-ecs-naming-convention/271744/1 "2021-04-30T07:19:30Z")

</div>

we're indexing syslogs data via Logstash (without Filebeat).  
Since it's not that clear, how Logstash manages ECS schema, I checked the Filebeat mapping and realized, that it uses different naming for [Syslog](https://www.elastic.co/guide/en/beats/filebeat/current/exported-fields-system.html#_syslog): `system.syslog.*`  
[ECS syslog](https://www.elastic.co/guide/en/ecs/1.9/ecs-log.html) fields starts from: `log.syslog.*`

Questions:

1. what is the correct mapping (ECS or Filebeat docu)?
2. can Logstash remap the standard `syslog` fields to ECS ones  
(e.g. `timereported` -\> `@timestamp`, `syslogseverity-text` -\> `log.syslog.severity.name`) or do we need to "re-invent the wheel"?

Thanks a lot!

---

<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:** [May 28, 2021, 7:19am UTC](https://discuss.elastic.co/t/ecs-for-syslog-why-filebeat-does-not-follow-ecs-naming-convention/271744/2 "2021-05-28T07:19:52Z")

</div>

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