# X-Pack Alerting
**URL:** https://discuss.elastic.co/t/x-pack-alerting/98833
**Category:** Elasticsearch
**Created:** [August 30, 2017, 10:00am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833 "2017-08-30T10:00:36Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [August 30, 2017, 10:00am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/1 "2017-08-30T10:00:36Z")
In a multi node elastic cluster which node (master, hot and warm data nodes, client nodes) the following mail configuration needs to be entered for X-Pack alerting.
xpack.notification.email.account:
work:
profile: gmail
email\_defaults:
from:
smtp:
auth: true
starttls.enable: true
host: [smtp.gmail.com](http://smtp.gmail.com)
port: 587
user:
password:
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [August 31, 2017, 10:13am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/2 "2017-08-31T10:13:10Z")
Hi @mruthyu,
what is your question regarding the mentioned alerting configuration?
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [August 31, 2017, 11:02am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/3 "2017-08-31T11:02:30Z")
Whether the above mentioned email account configuration needs to be entered (elasticsearch.yml) on all nodes or only in the master nodes is fine where the watcher runs.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [August 31, 2017, 12:03pm UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/4 "2017-08-31T12:03:38Z")
For the sake of consistency you should put it on all nodes. You **have to** put it on all nodes that can potentially become master node. Also, from 6.0 onwards the location where watches will be executed will change, so that it makes sense to put this config everywhere just to be future proof.
If you dont want to store this in configuration files, you can also use the [cluster update settings API](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/cluster-update-settings.html) to store the configuration settings. No need for a restart.
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [September 1, 2017, 11:44am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/5 "2017-09-01T11:44:32Z")
Great. Thank you. Where the persistent type of cluster updates are stored? Whether it will survive the node restart.
Also when is the tentative date of BELK 6.0 release.
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [September 1, 2017, 12:21pm UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/6 "2017-09-01T12:21:03Z")
AFAIK the settings become part of the cluster state.
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [September 1, 2017, 1:45pm UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/7 "2017-09-01T13:45:12Z")
Felix is right. The persistent updates are written to disk together with the cluster state. This is also the reason why those updates survive full cluster restarts, where as the transient updates do not.
There are no concrete release dates for the Elastic Stack 6.0. Even though we are nearing GA, it will take a few more months until the GA version will be out (and one or more release candidates in between). Nothing more concrete though.
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [September 6, 2017, 9:55am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/8 "2017-09-06T09:55:14Z")
Thank you.
---
### Author:  [@mruthyu](https://discuss.elastic.co/u/mruthyu)
#### Post date: [September 6, 2017, 10:22am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/9 "2017-09-06T10:22:04Z")
Let me know if the following is fine for persistent settings.
PUT /\_cluster/settings
{
"persistent" : {
"xpack.notification.email.account.standard\_account.profile" : "standard",
"xpack.notification.email.account.standard\_account.email\_defaults.from" : "XXXXX@EMAIL.COM",
"xpack.notification.email.account.standard\_account.smtp.auth" : "false",
"xpack.notification.email.account.standard\_account.smtp.starttls.enable" : "false",
"xpack.notification.email.account.standard\_account.smtp.host" : "10.11.1.16",
"xpack.notification.email.account.standard\_account.smtp.port" : "50"
}
}
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [September 8, 2017, 9:10am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/10 "2017-09-08T09:10:21Z")
you should see a logging line starting like this in your master node
```auto
[2017-09-08T11:08:48,979][INFO][o.e.c.s.ClusterSettings] [YtxeOyz] updating [xpack.notification.email.]
```
you can just check if `GET /_cluster/settings` for your settings.
--Alex
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 6, 2017, 9:10am UTC](https://discuss.elastic.co/t/x-pack-alerting/98833/11 "2017-10-06T09:10:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.