Skip to content

Out of the box ECS field mappings for Custom Input packages #4236

@P1llus

Description

@P1llus

Currently the custom input packages (like TCP/UDP, httpjson etc) comes with the bare minimum of ECS mapping, very similar to how custom inputs worked in Filebeat, however this does not produce the best outcome for the end users, as functionality like add_*_metadata for example produces ECS fields, especially host which is enabled by default.

This issue is to discuss what the best practice would be for all Custom Input packages, and then used to track the status of applying any decided changes.

Packages:

  • httpjson
  • http_endpoint
  • eventhub
  • s3
  • tcp
  • udp
  • filestream
  • log
  • kafka
  • winlog

Metadata

Metadata

Assignees

No one assigned

    Labels

    StalledTeam:Obs-InfraObsObservability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]Team:Security-Deployment and DevicesDEPRECATED Deployment and Devices Security team [elastic/sec-deployment-and-devices]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Team:Security-Windows PlatformSecurity Windows Platform team [elastic/sec-windows-platform]discuss

    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