fields yaml files typos

[efd6]

While working on a package/ECS yaml file analyser I found a collection of field name typos in a variety of field description files:

• default_fields (?) — packages/network_traffic/data_stream/tls/fields/protocol.yml
• descriiption — packages/mimecast/data_stream/audit_events/fields/ecs.yml
• descripion —
  • packages/elastic_agent/data_stream/apm_server_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/auditbeat_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/elastic_agent_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/endpoint_security_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/filebeat_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/fleet_server_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/heartbeat_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/metricbeat_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/osquerybeat_metrics/fields/beat-fields.yml
  • packages/elastic_agent/data_stream/packetbeat_metrics/fields/beat-fields.yml
• dimensiont — packages/kubernetes/data_stream/state_replicaset/fields/base-fields.yml
• dimensions (?) — packages/kubernetes/data_stream/state_statefulset/fields/base-fields.yml

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[ruflin]

@jsoriano @mtojek Is this something we could potentially catch during validation?

[jsoriano]

Is this something we could potentially catch during validation?

I guess we could set additionalProperties: false in the fields spec, I have opened a PR for this: elastic/package-spec#281

Is there any reason to don't do this?

[ruflin]

As long as the spec is fully up-to-date with which fields are allowed, it should be fine. It likely will mean as soon as the package-spec is updated, some packages will need adjustment but this is a good thing.

[jsoriano]

I have created elastic/package-spec#282 to follow up on stricter validation of fields properties.

[botelastic]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!