Add observer and geo metadata
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
Use the heartbeat.run_from option to set the geographic location fields relevant to a given heartbeat instance.
The run_from option is used to label the geographic location where the monitor is running. Note, you can also set the run_from option on an individual monitor to apply a unique setting to just that monitor.
The run_from option takes two top-level fields:
id: A string used to uniquely identify the geographic location. It is indexed as theobserver.namefield.geo: A map conforming to ECS geo fields. It is indexed underobserver.geo.
Example:
heartbeat.run_from:
id: my-custom-geo
geo:
name: nyc-dc1-rack2
location: 40.7128, -74.0060
continent_name: North America
country_iso_code: US
region_name: New York
region_iso_code: NY
city_name: New York