Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

network_traffic: add notice for deprecation of map_to_ecs behaviour #9031

Merged
merged 1 commit into from
Feb 1, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions packages/network_traffic/_dev/build/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,29 @@ Currently, Network Packet Capture supports the following protocols:

The following options are available for all protocols:

#### `map_to_ecs`

Remap any non-ECS Packetbeat fields in root to their correct ECS fields.
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.

The legacy behaviour of this option is to not remap to ECS. This behaviour
is still the default, but is deprecated and users are encouraged to set
this option to true.

ECS remapping may have an impact on workflows that depend on the identity
of non-ECS fields, and users should assess their use of these fields before
making the change. Users who need to retain data collected with the legacy
mappings may need to re-index their older documents. Instructions for doing
this are available [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html).
The pipeline used to perform ECS remapping for each data stream can be found
in `Stack Management`›`Ingest Pipelines` and and searching for
"logs-network_traffic compatibility".

The deprecation and retirement timeline for legacy behavior is available
[here](https://github.com/elastic/integrations/issues/8185).

#### `enabled`

The enabled setting is a boolean setting to enable or disable protocols
Expand Down
5 changes: 5 additions & 0 deletions packages/network_traffic/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "1.30.0"
changes:
- description: Publish deprecation notice for legacy behavior of `map_to_ecs`.
type: enhancement
link: https://github.com/elastic/integrations/pull/9031
- version: "1.29.1"
changes:
- description: Changed owners
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/amqp/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: AMQP
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: Cassandra
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/dhcpv4/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: DHCP
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/dns/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: DNS
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/flow/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,9 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/http/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: HTTP
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/icmp/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,9 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: Memcached
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/mongodb/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: MongoDB
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/mysql/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: MySQL
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/nfs/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: NFS
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/pgsql/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: PostgreSQL
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/redis/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: Redis
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/sip/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: SIP
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/thrift/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: Thrift
Expand Down
5 changes: 4 additions & 1 deletion packages/network_traffic/data_stream/tls/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,10 @@ streams:
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.
show_user: false

The legacy behaviour of this option is deprecated and users are encouraged
to set this option to true. See details in the [package overview describing `map_to_ecs`](../../../integrations/detail/network_traffic/overview).
show_user: true
multi: false
required: false
title: TLS
Expand Down
23 changes: 23 additions & 0 deletions packages/network_traffic/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,29 @@ Currently, Network Packet Capture supports the following protocols:

The following options are available for all protocols:

#### `map_to_ecs`

Remap any non-ECS Packetbeat fields in root to their correct ECS fields.
This will rename fields that are moved so the fields will not be present
at the root of the document and so any rules that depend on the fields
will need to be updated.

The legacy behaviour of this option is to not remap to ECS. This behaviour
is still the default, but is deprecated and users are encouraged to set
this option to true.

ECS remapping may have an impact on workflows that depend on the identity
of non-ECS fields, and users should assess their use of these fields before
making the change. Users who need to retain data collected with the legacy
mappings may need to re-index their older documents. Instructions for doing
this are available [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html).
The pipeline used to perform ECS remapping for each data stream can be found
in `Stack Management`›`Ingest Pipelines` and and searching for
"logs-network_traffic compatibility".

The deprecation and retirement timeline for legacy behavior is available
[here](https://github.com/elastic/integrations/issues/8185).

#### `enabled`

The enabled setting is a boolean setting to enable or disable protocols
Expand Down
2 changes: 1 addition & 1 deletion packages/network_traffic/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: "3.0.0"
name: network_traffic
title: Network Packet Capture
version: "1.29.1"
version: "1.30.0"
description: Capture and analyze network traffic from a host with Elastic Agent.
type: integration
categories:
Expand Down