Skip to content

Update TLS protocol to use ECS fields#9980

Merged
andrewkroh merged 2 commits intoelastic:masterfrom
andrewkroh:feature/pb/tls-ecs-fields
Jan 14, 2019
Merged

Update TLS protocol to use ECS fields#9980
andrewkroh merged 2 commits intoelastic:masterfrom
andrewkroh:feature/pb/tls-ecs-fields

Conversation

@andrewkroh
Copy link
Copy Markdown
Member

@andrewkroh andrewkroh commented Jan 10, 2019

NOTE: This is based on another open PR so please only review the last commit

That dashboards were updated too. There weren't many changes needed w.r.t. fields
but I did update the visualizations and saved searches to include [Packetbeat] in their
names.

I added a python test case for TLS and discovered a few fields that were not documented
so I updated the fields docs accordingly.

Here's a summary of what fields changed.

Part of #7968

Changed

  • responsetime -> event.duration (unit are now nanoseconds)

Added

  • event.dataset = tls
  • event.end
  • event.start
  • network.community_id
  • network.protocol = tls
  • network.type
  • source.domain (added if there's a SNI value)

Unchanged Packetbeat Fields

  • status
  • type = http (we might remove this since we have event.dataset)

Copy link
Copy Markdown
Contributor

@adriansr adriansr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for the improvements and new tests!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I added this to the dashboard while creating it. Can you remove it?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@andrewkroh andrewkroh force-pushed the feature/pb/tls-ecs-fields branch from 96d4f34 to fbb8a1a Compare January 10, 2019 15:26
That dashboards were updated too. There weren't many changes needed w.r.t. fields
but I did update the visualizations and saved searches to include `[Packetbeat]` in their
names.

I added a python test case for TLS and discovered a few fields that were not documented
so I updated the fields docs accordingly.

Here's a summary of what fields changed.

Part of elastic#7968

Changed

- responsetime -> event.duration (unit are now nanoseconds)

Added

- event.dataset = tls
- event.end
- event.start
- network.community_id
- network.protocol = tls
- network.type
- source.domain (added if there's a SNI value)

Unchanged Packetbeat Fields

- status
- type = http (we might remove this since we have event.dataset)
@andrewkroh andrewkroh force-pushed the feature/pb/tls-ecs-fields branch from fbb8a1a to e0c1a4f Compare January 10, 2019 15:28
@andrewkroh andrewkroh merged commit c956b80 into elastic:master Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants