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

[Filebeat] Upgrade nats module to ECS 1.4 #16173

Closed
1 task
leehinman opened this issue Feb 6, 2020 · 1 comment · Fixed by #17550
Closed
1 task

[Filebeat] Upgrade nats module to ECS 1.4 #16173

leehinman opened this issue Feb 6, 2020 · 1 comment · Fixed by #17550
Assignees

Comments

@leehinman
Copy link
Contributor

Filesets

  • log
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@leehinman leehinman self-assigned this Apr 3, 2020
leehinman added a commit to leehinman/beats that referenced this issue Apr 6, 2020
- event.kind
- event.type
- related.ip

Closes elastic#16173
leehinman added a commit that referenced this issue Apr 16, 2020
…17550)

* Improve ECS categorization field mappings for nats module

- event.kind
- event.type
- related.ip

Closes #16173
leehinman added a commit to leehinman/beats that referenced this issue Apr 16, 2020
…lastic#17550)

* Improve ECS categorization field mappings for nats module

- event.kind
- event.type
- related.ip

Closes elastic#16173

(cherry picked from commit eb5ba9a)
leehinman added a commit to leehinman/beats that referenced this issue Apr 16, 2020
…lastic#17550)

* Improve ECS categorization field mappings for nats module

- event.kind
- event.type
- related.ip

Closes elastic#16173

(cherry picked from commit eb5ba9a)
leehinman added a commit that referenced this issue Apr 16, 2020
…17550) (#17755)

* Improve ECS categorization field mappings for nats module

- event.kind
- event.type
- related.ip

Closes #16173

(cherry picked from commit eb5ba9a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants