Unable to include fields present in index while using email action in watcher

This is my hearbeat configuration

Directory + glob pattern to search for configuration files

path: ${path.config}/monitors.d/*.yml

If enabled, heartbeat will periodically check the config.monitors path for changes

reload.enabled: false

How often to check for changes

reload.period: 5s

Configure monitors inline



certificate_authorities: ['/home/actived/cert/onlineregistration_org.cer']

supported_protocols: ["TLSv1.0", "TLSv1.1", "TLSv1.2"]

Total test connection and data exchange timeout

#timeout: 16s

#==================== Elasticsearch template setting ==========================

index.number_of_shards: 1
index.codec: best_compression
#_source.enabled: false

#================================ General =====================================

The name of the shipper that publishes the network data. It can be used to group

all the transactions sent by a single shipper in the web interface.


The tags of the shipper are included in their own field with each

transaction published.

#tags: ["service-X", "web-tier"]

Optional fields that you can specify to add additional information to the



env: staging

#============================== Dashboards =====================================

These settings control loading the sample dashboards to the Kibana index. Loading

the dashboards is disabled by default and can be enabled either by setting the

options here, or by using the -setup CLI flag or the setup command.

#setup.dashboards.enabled: false

The URL from where to download the dashboards archive. By default this URL

has a value which is computed based on the Beat name and version. For released

versions, this URL points to the dashboard archive on the artifacts.elastic.co



#============================== Kibana =====================================

Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

This requires a Kibana endpoint configuration.


Kibana Host

Scheme and port can be left out and will be set to the default (http and 5601)

In case you specify and additional path, the scheme is required: http://localhost:5601/path

IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

#host: "localhost:5601"

Kibana Space ID

ID of the Kibana Space into which the dashboards should be loaded. By default,

the Default Space will be used.


#============================= Elastic Cloud ==================================

These settings simplify using heartbeat with the Elastic Cloud (https://cloud.elastic.co/).

The cloud.id setting overwrites the output.elasticsearch.hosts and

setup.kibana.host options.

You can find the cloud.id in the Elastic Cloud web UI.


The cloud.auth setting overwrites the output.elasticsearch.username and

output.elasticsearch.password settings. The format is <user>:<pass>.


#================================ Outputs =====================================

Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------

Array of hosts to connect to.

hosts: [""]

Enabled ilm (beta) to use index lifecycle management instead daily indices.

#ilm.enabled: false

Optional protocol and basic auth credentials.

#protocol: "https"
username: "elastic"
password: "password"
#----------------------------- Logstash output --------------------------------

The Logstash hosts

#hosts: ["localhost:5044"]

Optional SSL. By default is off.

List of root certificates for HTTPS server verifications

#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

#================================ Processors =====================================

Configure processors to enhance or manipulate events generated by the beat.


  • add_host_metadata: ~
  • add_cloud_metadata: ~

#================================ Logging =====================================

Sets log level. The default log level is info.

Available log levels are: error, warning, info, debug

#logging.level: debug

At debug level, you can selectively enable logging only for some components.

To enable all selectors use ["*"]. Examples of other selectors are "beat",

"publish", "service".

#logging.selectors: ["*"]

#============================== Xpack Monitoring ===============================

heartbeat can export internal metrics to a central Elasticsearch monitoring

cluster. This requires xpack monitoring to be enabled in Elasticsearch. The

reporting is disabled by default.

Set to true to enable the monitoring reporter.

#xpack.monitoring.enabled: false

Uncomment to send the metrics to Elasticsearch. Most settings from the

Elasticsearch output are accepted here as well. Any setting that is not set is

automatically inherited from the Elasticsearch output configuration, so if you

have the Elasticsearch output configured, you can simply uncomment the

following line.

#xpack.monitoring.elasticsearch:Preformatted text

PUT _xpack/watcher/watch/my-watch1

"trigger" : {
"schedule" : { "cron" : "0 0/1 * * * ?" }
"input" : {
"search" : {
"request" : {
"indices" : [
"body" : {
"query" : {
"bool" : {
"must": [
"term": {
"monitor.status": {
"value": "down"
"filter" : {
"range": {
"@timestamp": {
"from": "{{ctx.trigger.scheduled_time}}||-5m",
"to": "{{ctx.trigger.triggered_time}}"
"condition" : {
"compare" : { "ctx.payload.hits.total" : { "gt" : 0 }}
"actions" : {
"email_admin" : {
"email" : {
"to" : "vishnumk@nseit.com",
"subject" : "down",
"body" : "{{ctx.payload.http.url}}"

I am receiving the mail when portal is down but im not receiving the http.url field from heartbeat index in my mail


please format your posts properly, you can use markdown code formatting in here - which makes your posts a million times easier to read, which in turn increases the likelihood of getting an answer. Thank you!

Also, I highly encourage you to read this blog post about debugging watches, as it will likely reduce the time you spent on debugging.

Lastly, the payload you are receiving looks exactly like a search request, which means that the data about single hits is included in ctx.payload.hits.hits array. Just execute that search via the dev tools console and see how the search response data structure looks like.

Hope this helps!


"hits" : {
"hits" : [
"_index" : "heartbeat-6.7.0-2019.05.08",
"_type" : "doc",
"_source" : {
"tcp" : {
"port" : 8081
"@timestamp" : "2019-05-08T12:49:43.243Z",
"beat" : {
"hostname" : "dbserver1",
"name" : "dbserver1",
"version" : "6.7.0"
"host" : {
"os" : {
"codename" : "Core",
"name" : "CentOS Linux",
"family" : "redhat",
"version" : "7 (Core)",
"platform" : "centos"
"containerized" : true,
"name" : "dbserver1",
"id" : "40adb1a64eaa4d0cb8f9c45422250ca2",
"architecture" : "x86_64"
"http" : {
"url" : ""
"monitor" : {
"duration" : {
"us" : 16000287
"scheme" : "http",
"ip" : "",
"name" : "http",
"id" : "http@",
"type" : "http",
"status" : "down"
"event" : {
"dataset" : "uptime"

Please help me out how can i get my http.url field

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.