# Notify slack action configuration not loading under ES 6.6 with new secure\_url setting

**URL:** <https://discuss.elastic.co/t/notify-slack-action-configuration-not-loading-under-es-6-6-with-new-secure-url-setting/169050>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [February 19, 2019, 3:23pm UTC](https://discuss.elastic.co/t/notify-slack-action-configuration-not-loading-under-es-6-6-with-new-secure-url-setting/169050 "2019-02-19T15:23:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticdave](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@elasticdave](https://discuss.elastic.co/u/elasticdave)\
**Post date:** [February 19, 2019, 3:23pm UTC](https://discuss.elastic.co/t/notify-slack-action-configuration-not-loading-under-es-6-6-with-new-secure-url-setting/169050/1 "2019-02-19T15:23:51Z")

</div>

Hello,

Since updating to Elasticsearch 6.6 I am unable to make use of the slack action. I've reviewed the breaking changes and found that the 'url' setting has been deprecated in favor of the new 'secure\_url' setting that must be stored in the elasticsearch-keystore. The resultant message of a test execution is that no slack accounts are configured.

I've loaded my Slack webhook url into the specified setting referenced in the documentation using the syntax as follows:

`bin/elasticsearch-keystore add xpack.notification.slack.account.monitoring.secure_url`

At minimum you were historically only required to include the url for slack actions to function. With this new method of storage in the keystore there is nothing at all configured via the yml in my environment for slack actions.

The results of a configuration check filtered to xpack.notifcations returns no trace of any slack settings on any nodes.

`GET _nodes?filter_path=**.settings.xpack.notification`

My uneducated guess is that with nothing configured in the elasticsearch.yml, elastic does not 'load' my secure\_url setting. Am I missing an xpack.notification.slack: true type flag of some sort?

[https://www.elastic.co/guide/en/elastic-stack-overview/current/actions-slack.html](https://www.elastic.co/guide/en/elastic-stack-overview/current/actions-slack.html)

---

<div class="post-metadata">

**Author:** ![elasticdave](https://avatars.discourse-cdn.com/v4/letter/e/ecae2f/32.png) [@elasticdave](https://discuss.elastic.co/u/elasticdave)\
**Post date:** [February 19, 2019, 8:22pm UTC](https://discuss.elastic.co/t/notify-slack-action-configuration-not-loading-under-es-6-6-with-new-secure-url-setting/169050/2 "2019-02-19T20:22:57Z")

</div>

I added a default setting to elasticsearch.yml and it picked up the secure\_url setting. Looks like you need something in the yml in order for elasticsearch to load any settings stored in the keystore.

```
xpack.notification.slack:
    account:
        monitoring:
            message_defaults:
                title: "Test Alert"
```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 19, 2019, 8:33pm UTC](https://discuss.elastic.co/t/notify-slack-action-configuration-not-loading-under-es-6-6-with-new-secure-url-setting/169050/3 "2019-03-19T20:33:47Z")

</div>

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