# Can't start kibana when enabling preconfigured alert history

**URL:** <https://discuss.elastic.co/t/cant-start-kibana-when-enabling-preconfigured-alert-history/276946>\
**Category:** Kibana\
**Tags:** elastic-stack-alerting\
**Created:** [June 24, 2021, 2:25pm UTC](https://discuss.elastic.co/t/cant-start-kibana-when-enabling-preconfigured-alert-history/276946 "2021-06-24T14:25:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![marone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marone/32/87145_2.png) [@marone](https://discuss.elastic.co/u/marone)\
**Post date:** [June 24, 2021, 2:25pm UTC](https://discuss.elastic.co/t/cant-start-kibana-when-enabling-preconfigured-alert-history/276946/1 "2021-06-24T14:25:53Z")

</div>

I am using elastic stack 7.12.0 and enabled alerting specifying a value for `xpack.encryptedSavedObjects.encryptionKey` in `kibana.yml`. At this stage alerting works well with **Server log connector**. When I tried to activate [Alert history Elasticsearch index connector](https://www.elastic.co/guide/en/kibana/current/index-action-type.html#preconfigured-connector-alert-history) enabling the `xpack.actions.preconfiguredAlertHistoryEsIndex` to `true` in `kibana.yml`, Kibana service won't start and logs aren't showing any error related to configuration. How to use predefined index for alerting please?

---

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [June 29, 2021, 2:17pm UTC](https://discuss.elastic.co/t/cant-start-kibana-when-enabling-preconfigured-alert-history/276946/2 "2021-06-29T14:17:21Z")

</div>

I believe the preconfigured alert history connector is only available in Kibana 7.13.0 and later, given the labels in the pull request where it was added: [https://github.com/elastic/kibana/pull/94909](https://github.com/elastic/kibana/pull/94909)

It seems like you should have gotten an error message when starting Kibana indicating an invalid config key. I think those are typically printed very early, so wondering if the log output didn't get collected before the process terminated.

---

<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:** [July 27, 2021, 2:17pm UTC](https://discuss.elastic.co/t/cant-start-kibana-when-enabling-preconfigured-alert-history/276946/3 "2021-07-27T14:17:37Z")

</div>

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