Skip to content

Make the .name pattern more obvious #269

@webmat

Description

@webmat

Some of the .name fields in ECS are meant to be user-overridable, and to default to the value of another field when not overridden.

I don't think this pattern is expressed clearly enough yet, when this happens. We should try to illustrate this better.

Here are the fields and their "default value" sister field:

  • host.name defaults to host.hostname
  • agent.name defaults to agent.type
  • service.name defaults to service.type

Metadata

Metadata

Assignees

No one assigned

    Labels

    readyIssues we'd like to address in the future.

    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