Remove deprecated fields

Remove deprecated fields from the previous major release: * process.parent.pgid * process.pgid * service.node.role * service.origin.node.role * service.target.node.role
elastic · Dec 6, 2024 · 4ee0e79 · 4ee0e79
1 parent 9f1658a
commit 4ee0e79
Show file tree

Hide file tree

Showing 19 changed files with 2 additions and 710 deletions.
diff --git a/CHANGELOG.next.md b/CHANGELOG.next.md
@@ -12,6 +12,8 @@ Thanks, you're awesome :-) -->
 
 #### Breaking changes
 
+* Remove deprecated fields from previous major release; `process.pgid`, `service.node.role`, and inherited users. #999999
+
 #### Bugfixes
 
 #### Added

diff --git a/docs/fields/field-details.asciidoc b/docs/fields/field-details.asciidoc
@@ -8405,24 +8405,6 @@ Multi-fields:
 
 example: `ssh`
 
-| extended
-
-// ===============================================================
-
-|
-[[field-process-pgid]]
-<<field-process-pgid, process.pgid>>
-
-a| Deprecated for removal in next major version release. This field is superseded by `process.group_leader.pid`.
-
-Identifier of the group of processes the process belongs to.
-
-type: long
-
-
-
-
-
 | extended
 
 // ===============================================================
@@ -9913,32 +9895,6 @@ example: `instance-0000000016`
 
 // ===============================================================
 
-|
-[[field-service-node-role]]
-<<field-service-node-role, service.node.role>>
-
-a| Deprecated for removal in next major version release. This field will be superseded by `node.roles`.
-
-Role of a service node.
-
-This allows for distinction between different running roles of the same service.
-
-In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-In the case of Elasticsearch, the `service.node.role` could be `master` or `data`.
-
-Other services could use this to distinguish between a `web` and `worker` role running as part of the service.
-
-type: keyword
-
-
-
-example: `background_tasks`
-
-| extended
-
-// ===============================================================
-
 |
 [[field-service-node-roles]]
 <<field-service-node-roles, service.node.roles>>

diff --git a/experimental/generated/beats/fields.ecs.yml b/experimental/generated/beats/fields.ecs.yml
@@ -6897,15 +6897,6 @@
       format: string
       description: PE Section List virtual size. This is always the same as `physical_size`.
       default_field: false
-    - name: parent.pgid
-      level: extended
-      type: long
-      format: string
-      description: 'Deprecated for removal in next major version release. This field
-        is superseded by `process.group_leader.pid`.
-
-        Identifier of the group of processes the process belongs to.'
-      default_field: false
     - name: parent.pid
       level: core
       type: long
@@ -7269,14 +7260,6 @@
       format: string
       description: PE Section List virtual size. This is always the same as `physical_size`.
       default_field: false
-    - name: pgid
-      level: extended
-      type: long
-      format: string
-      description: 'Deprecated for removal in next major version release. This field
-        is superseded by `process.group_leader.pid`.
-
-        Identifier of the group of processes the process belongs to.'
     - name: pid
       level: core
       type: long
@@ -8445,26 +8428,6 @@
         provide uniqueness (e.g. multiple instances of the service running on the
         same host) - the node name can be manually set.'
       example: instance-0000000016
-    - name: node.role
-      level: extended
-      type: keyword
-      ignore_above: 1024
-      description: 'Deprecated for removal in next major version release. This field
-        will be superseded by `node.roles`.
-
-        Role of a service node.
-
-        This allows for distinction between different running roles of the same service.
-
-        In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-        In the case of Elasticsearch, the `service.node.role` could be `master` or
-        `data`.
-
-        Other services could use this to distinguish between a `web` and `worker`
-        role running as part of the service.'
-      example: background_tasks
-      default_field: false
     - name: node.roles
       level: extended
       type: keyword
@@ -8561,26 +8524,6 @@
         same host) - the node name can be manually set.'
       example: instance-0000000016
       default_field: false
-    - name: origin.node.role
-      level: extended
-      type: keyword
-      ignore_above: 1024
-      description: 'Deprecated for removal in next major version release. This field
-        will be superseded by `node.roles`.
-
-        Role of a service node.
-
-        This allows for distinction between different running roles of the same service.
-
-        In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-        In the case of Elasticsearch, the `service.node.role` could be `master` or
-        `data`.
-
-        Other services could use this to distinguish between a `web` and `worker`
-        role running as part of the service.'
-      example: background_tasks
-      default_field: false
     - name: origin.node.roles
       level: extended
       type: keyword
@@ -8710,26 +8653,6 @@
         same host) - the node name can be manually set.'
       example: instance-0000000016
       default_field: false
-    - name: target.node.role
-      level: extended
-      type: keyword
-      ignore_above: 1024
-      description: 'Deprecated for removal in next major version release. This field
-        will be superseded by `node.roles`.
-
-        Role of a service node.
-
-        This allows for distinction between different running roles of the same service.
-
-        In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-        In the case of Elasticsearch, the `service.node.role` could be `master` or
-        `data`.
-
-        Other services could use this to distinguish between a `web` and `worker`
-        role running as part of the service.'
-      example: background_tasks
-      default_field: false
     - name: target.node.roles
       level: extended
       type: keyword

diff --git a/experimental/generated/csv/fields.csv b/experimental/generated/csv/fields.csv
@@ -884,7 +884,6 @@ ECS_Version,Indexed,Field_Set,Field,Type,Level,Normalization,Example,Description
 9.0.0-dev+exp,true,process,process.parent.pe.sections.physical_size,long,extended,,,PE Section List physical size.
 9.0.0-dev+exp,true,process,process.parent.pe.sections.var_entropy,long,extended,,,Variance for Shannon entropy calculation from the section.
 9.0.0-dev+exp,true,process,process.parent.pe.sections.virtual_size,long,extended,,,PE Section List virtual size. This is always the same as `physical_size`.
-9.0.0-dev+exp,true,process,process.parent.pgid,long,extended,,,Deprecated identifier of the group of processes the process belongs to.
 9.0.0-dev+exp,true,process,process.parent.pid,long,core,,4242,Process id.
 9.0.0-dev+exp,true,process,process.parent.real_group.id,keyword,extended,,,Unique identifier for the group on the system/platform.
 9.0.0-dev+exp,true,process,process.parent.real_group.name,keyword,extended,,,Name of the group.
@@ -938,7 +937,6 @@ ECS_Version,Indexed,Field_Set,Field,Type,Level,Normalization,Example,Description
 9.0.0-dev+exp,true,process,process.pe.sections.physical_size,long,extended,,,PE Section List physical size.
 9.0.0-dev+exp,true,process,process.pe.sections.var_entropy,long,extended,,,Variance for Shannon entropy calculation from the section.
 9.0.0-dev+exp,true,process,process.pe.sections.virtual_size,long,extended,,,PE Section List virtual size. This is always the same as `physical_size`.
-9.0.0-dev+exp,true,process,process.pgid,long,extended,,,Deprecated identifier of the group of processes the process belongs to.
 9.0.0-dev+exp,true,process,process.pid,long,core,,4242,Process id.
 9.0.0-dev+exp,true,process,process.previous.args,keyword,extended,array,"[""/usr/bin/ssh"", ""-l"", ""user"", ""10.0.0.16""]",Array of process arguments.
 9.0.0-dev+exp,true,process,process.previous.args_count,long,extended,,4,Length of the process.args array.
@@ -1084,15 +1082,13 @@ ECS_Version,Indexed,Field_Set,Field,Type,Level,Normalization,Example,Description
 9.0.0-dev+exp,true,service,service.id,keyword,core,,d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6,Unique identifier of the running service.
 9.0.0-dev+exp,true,service,service.name,keyword,core,,elasticsearch-metrics,Name of the service.
 9.0.0-dev+exp,true,service,service.node.name,keyword,extended,,instance-0000000016,Name of the service node.
-9.0.0-dev+exp,true,service,service.node.role,keyword,extended,,background_tasks,Deprecated role (singular) of the service node.
 9.0.0-dev+exp,true,service,service.node.roles,keyword,extended,array,"[""ui"", ""background_tasks""]",Roles of the service node.
 9.0.0-dev+exp,true,service,service.origin.address,keyword,extended,,172.26.0.2:5432,Address of this service.
 9.0.0-dev+exp,true,service,service.origin.environment,keyword,extended,,production,Environment of the service.
 9.0.0-dev+exp,true,service,service.origin.ephemeral_id,keyword,extended,,8a4f500f,Ephemeral identifier of this service.
 9.0.0-dev+exp,true,service,service.origin.id,keyword,core,,d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6,Unique identifier of the running service.
 9.0.0-dev+exp,true,service,service.origin.name,keyword,core,,elasticsearch-metrics,Name of the service.
 9.0.0-dev+exp,true,service,service.origin.node.name,keyword,extended,,instance-0000000016,Name of the service node.
-9.0.0-dev+exp,true,service,service.origin.node.role,keyword,extended,,background_tasks,Deprecated role (singular) of the service node.
 9.0.0-dev+exp,true,service,service.origin.node.roles,keyword,extended,array,"[""ui"", ""background_tasks""]",Roles of the service node.
 9.0.0-dev+exp,true,service,service.origin.state,keyword,core,,,Current state of the service.
 9.0.0-dev+exp,true,service,service.origin.type,keyword,core,,elasticsearch,The type of the service.
@@ -1104,7 +1100,6 @@ ECS_Version,Indexed,Field_Set,Field,Type,Level,Normalization,Example,Description
 9.0.0-dev+exp,true,service,service.target.id,keyword,core,,d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6,Unique identifier of the running service.
 9.0.0-dev+exp,true,service,service.target.name,keyword,core,,elasticsearch-metrics,Name of the service.
 9.0.0-dev+exp,true,service,service.target.node.name,keyword,extended,,instance-0000000016,Name of the service node.
-9.0.0-dev+exp,true,service,service.target.node.role,keyword,extended,,background_tasks,Deprecated role (singular) of the service node.
 9.0.0-dev+exp,true,service,service.target.node.roles,keyword,extended,array,"[""ui"", ""background_tasks""]",Roles of the service node.
 9.0.0-dev+exp,true,service,service.target.state,keyword,core,,,Current state of the service.
 9.0.0-dev+exp,true,service,service.target.type,keyword,core,,elasticsearch,The type of the service.

diff --git a/experimental/generated/ecs/ecs_flat.yml b/experimental/generated/ecs/ecs_flat.yml
@@ -11279,20 +11279,6 @@ process.parent.pe.sections.virtual_size:
   original_fieldset: pe
   short: PE Section List virtual size. This is always the same as `physical_size`.
   type: long
-process.parent.pgid:
-  dashed_name: process-parent-pgid
-  description: 'Deprecated for removal in next major version release. This field is
-    superseded by `process.group_leader.pid`.
-
-    Identifier of the group of processes the process belongs to.'
-  flat_name: process.parent.pgid
-  format: string
-  level: extended
-  name: pgid
-  normalize: []
-  original_fieldset: process
-  short: Deprecated identifier of the group of processes the process belongs to.
-  type: long
 process.parent.pid:
   dashed_name: process-parent-pid
   description: Process id.
@@ -11906,19 +11892,6 @@ process.pe.sections.virtual_size:
   original_fieldset: pe
   short: PE Section List virtual size. This is always the same as `physical_size`.
   type: long
-process.pgid:
-  dashed_name: process-pgid
-  description: 'Deprecated for removal in next major version release. This field is
-    superseded by `process.group_leader.pid`.
-
-    Identifier of the group of processes the process belongs to.'
-  flat_name: process.pgid
-  format: string
-  level: extended
-  name: pgid
-  normalize: []
-  short: Deprecated identifier of the group of processes the process belongs to.
-  type: long
 process.pid:
   dashed_name: process-pid
   description: Process id.
@@ -13663,29 +13636,6 @@ service.node.name:
   normalize: []
   short: Name of the service node.
   type: keyword
-service.node.role:
-  dashed_name: service-node-role
-  description: 'Deprecated for removal in next major version release. This field will
-    be superseded by `node.roles`.
-
-    Role of a service node.
-
-    This allows for distinction between different running roles of the same service.
-
-    In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-    In the case of Elasticsearch, the `service.node.role` could be `master` or `data`.
-
-    Other services could use this to distinguish between a `web` and `worker` role
-    running as part of the service.'
-  example: background_tasks
-  flat_name: service.node.role
-  ignore_above: 1024
-  level: extended
-  name: node.role
-  normalize: []
-  short: Deprecated role (singular) of the service node.
-  type: keyword
 service.node.roles:
   dashed_name: service-node-roles
   description: 'Roles of a service node.
@@ -13817,30 +13767,6 @@ service.origin.node.name:
   original_fieldset: service
   short: Name of the service node.
   type: keyword
-service.origin.node.role:
-  dashed_name: service-origin-node-role
-  description: 'Deprecated for removal in next major version release. This field will
-    be superseded by `node.roles`.
-
-    Role of a service node.
-
-    This allows for distinction between different running roles of the same service.
-
-    In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-    In the case of Elasticsearch, the `service.node.role` could be `master` or `data`.
-
-    Other services could use this to distinguish between a `web` and `worker` role
-    running as part of the service.'
-  example: background_tasks
-  flat_name: service.origin.node.role
-  ignore_above: 1024
-  level: extended
-  name: node.role
-  normalize: []
-  original_fieldset: service
-  short: Deprecated role (singular) of the service node.
-  type: keyword
 service.origin.node.roles:
   dashed_name: service-origin-node-roles
   description: 'Roles of a service node.
@@ -14026,30 +13952,6 @@ service.target.node.name:
   original_fieldset: service
   short: Name of the service node.
   type: keyword
-service.target.node.role:
-  dashed_name: service-target-node-role
-  description: 'Deprecated for removal in next major version release. This field will
-    be superseded by `node.roles`.
-
-    Role of a service node.
-
-    This allows for distinction between different running roles of the same service.
-
-    In the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.
-
-    In the case of Elasticsearch, the `service.node.role` could be `master` or `data`.
-
-    Other services could use this to distinguish between a `web` and `worker` role
-    running as part of the service.'
-  example: background_tasks
-  flat_name: service.target.node.role
-  ignore_above: 1024
-  level: extended
-  name: node.role
-  normalize: []
-  original_fieldset: service
-  short: Deprecated role (singular) of the service node.
-  type: keyword
 service.target.node.roles:
   dashed_name: service-target-node-roles
   description: 'Roles of a service node.