Skip to content

Commit

Permalink
Mention ECS Mapper in the main documentation (#987)
Browse files Browse the repository at this point in the history
  • Loading branch information
DanRoscigno authored Oct 5, 2020
1 parent 1d32671 commit 76ec52d
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions docs/converting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,18 @@ Here's the recommended approach for converting an existing implementation to {ec
. Set `ecs.version` to the version of the schema you are conforming to. This will
allow you to upgrade your sources, pipelines and content (like dashboards)
smoothly in the future.

[float]
[[ecs-conv-spreasheet]]
==== Using a spreadsheet to plan your migration

Using a spreadsheet to plan the migration from pre-existing source fields to ECS
is a common practice. It's a good way to address each of your fields methodically among colleagues.

If the data source is either a structured log, or if you already have a pipeline
producing events with these non-ECS field names, the tool
https://github.com/elastic/ecs-mapper[ECS Mapper] may help you get started in performing all of these field renames.

After exporting your mapping spreadsheet to CSV, ECS Mapper will convert your field mapping
to equivalent pipelines for Beats, Elasticsearch, and Logstash. Learn more at
https://github.com/elastic/ecs-mapper[ECS Mapper].

0 comments on commit 76ec52d

Please sign in to comment.