Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Redis protocol to use ECS fields #10126

Merged
merged 2 commits into from
Jan 18, 2019

Commits on Jan 16, 2019

  1. Update Redis protocol to use ECS fields

    Here's a summary of what fields changed.
    
    Part of elastic#7968
    
    Changed
    
    - bytes_in -> source.bytes
    - bytes_out -> destination.bytes
    - responsetime -> event.duration (unit are now nanoseconds)
    - redis.error -> error.message (alias added)
    
    Added
    
    - source
    - destination
    - event.dataset = redis
    - event.end
    - event.start
    - network.community_id
    - network.transport = tcp
    - network.protocol = redis
    - network.bytes
    - network.type
    
    Unchanged Packetbeat Fields
    
    - method
    - resource
    - path
    - query
    - status
    - type = redis (we might remove this since we have event.dataset)
    andrewkroh committed Jan 16, 2019
    Configuration menu
    Copy the full SHA
    c3c54d8 View commit details
    Browse the repository at this point in the history

Commits on Jan 17, 2019

  1. Revert redis.error rename to error.message

    This made it hard to tell the difference between Packetbeat processing errors and protocol level errors.
    andrewkroh committed Jan 17, 2019
    Configuration menu
    Copy the full SHA
    c06b45e View commit details
    Browse the repository at this point in the history