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

Find a better solution for address/ip/domain #37

Open
widhalmt opened this issue Sep 26, 2022 · 0 comments
Open

Find a better solution for address/ip/domain #37

widhalmt opened this issue Sep 26, 2022 · 0 comments
Labels
feature New feature or request

Comments

@widhalmt
Copy link
Member

We have all three fields for client and server. ECS says, .address has to be set. If there's an IP address in that field, copy it into .ip and if it's a FQDN, copy it into .domain.

The problem we have is that sometimes one is set but the other is not. Or both are set. Or one is set to a dummy value like unkown or while the other has a valid value. The current implementation tries to always use the most meaningful information for .address but this ends up different values in address depending on what log event it is.

We could work around it in Kibana by never using .address but I'm not sure if that's feasible. I'm opening this issue to search for a better solution to this problem.

@widhalmt widhalmt added the feature New feature or request label Sep 26, 2022
widhalmt added a commit that referenced this issue Sep 27, 2022
widhalmt added a commit that referenced this issue Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant