Configure feature flags
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The Feature Flags section of the heartbeat.yml config file contains settings in Heartbeat that are disabled by default. These may include experimental features, changes to behaviors within Heartbeat, or settings that could cause a breaking change. For example a setting that changes information included in events might be inconsistent with the naming pattern expected in your configured Heartbeat output.
To enable any of the settings listed on this page, change the associated enabled flag from false to true.
features:
mysetting:
enabled: true
You can specify the following options in the features section of the heartbeat.yml config file:
Contains configuration for the FQDN reporting feature. When this feature is enabled, the fully-qualified domain name for the host is reported in the host.name field in events produced by Heartbeat.
This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
For FQDN reporting to work as expected, the hostname of the current host must either:
- Have a CNAME entry defined in DNS.
- Have one of its corresponding IP addresses respond successfully to a reverse DNS lookup.
If neither pre-requisite is satisfied, host.name continues to report the hostname of the current host as if the FQDN feature flag were not enabled.
Example configuration:
features:
fqdn:
enabled: true
Set to true to enable the FQDN reporting feature of Heartbeat. Defaults to false.