You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on elastic/beats#1070, and elastic/ecs#2122 the Elastic Agent should be able to report the FQDN on host.name. This should be configurable by a feature flag on the agent policy.
Describe a specific use case for the enhancement or feature:
There are cases in which different hosts share the same hostname but have different domains. Currently they have the same host.name values, which isn't ideal. Allowing to populate host.name with the FQDN solves that problem. ALso having it behind a feature flag won't make it a breaking change as the user will have the option to enable it or not.
@AndersonQ - Endpoint will need to be aware of this feature flag as well. How do you plan on adding it to the configuration. @brian-mckinney - since he is the expert in this area for Endpoint. I see your other PR now!! THANKS!!!
Describe the enhancement:
Following up on elastic/beats#1070, and elastic/ecs#2122 the Elastic Agent should be able to report the FQDN on
host.name
. This should be configurable by a feature flag on the agent policy.Describe a specific use case for the enhancement or feature:
There are cases in which different hosts share the same hostname but have different domains. Currently they have the same
host.name
values, which isn't ideal. Allowing to populatehost.name
with the FQDN solves that problem. ALso having it behind a feature flag won't make it a breaking change as the user will have the option to enable it or not.Implementation details
Feature flag generic config:
Feature flag for FQDN:
Related Issues:
The text was updated successfully, but these errors were encountered: