Skip to content

fields yaml files typos #2643

@efd6

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions