Open MakoWish opened 4 years ago
Pinging @elastic/integrations (Team:Integrations)
Pinging @elastic/siem (Team:SIEM)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
It would be nice if this gets fixed some day..
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
I totally forgot I even opened this. Since we use Logstash for all data processing, I just added a correction in my pipeline, so it has been "out of sight, out of mind". I currently use Ruby to force all data sources to report host.name
as the simple hostname, and host.hostname
as the FQDN.
EDIT: Oops! Me replying removed the Stalled
tag again. :-(
Eric
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
There is some solution for this now to make host.name lowercase fqdn, but still in beta and not standardized imho. Also in Agent the lowercasing was forgotten..
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform)
Winlogbeat reports the 'host.name' field as a FQDN when other Beats report 'host.name' just as 'hostname' (not a FQDN).
This difference between Beats agents creates difficulty in pivoting across data sources.