Skip to content

Standardize defining expected field values #1951

@ebeahan

Description

@ebeahan

Description

Create a new field attribute, expected_values, to capture recommended values for a given field.

Downstream schema consumers can validate integrations and mapped data against the expected_values. How expected values appear in the ECS field reference will also be standardized.

Sample usage

---
- name: faas
  fields:
    - name: trigger.type
      level: extended
      type: keyword
      short: The trigger for the function execution.
      expected_values:
        - http
        - pubsub
        - data source
        - timer
        - other
      description: >
        The trigger for the function execution.

Metadata

Metadata

Assignees

Labels

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