# Not able to configure Alerts in Kibana
**URL:** https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765
**Category:** Kibana
**Tags:** elastic-stack-alerting
**Created:** [September 16, 2020, 4:48am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765 "2020-09-16T04:48:18Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 4:48am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/1 "2020-09-16T04:48:18Z")
Hi,
Can someone please help me to enable Alerts and Action option in Kibana as showing Additional setup required, I tried few settings but didn't work.
If anyone can provide me the configuration which needs to be change in Kibana and elastic search yml file that will be much appreciated.
---
### Author:  [@Funky89](https://discuss.elastic.co/u/Funky89)
#### Post date: [September 16, 2020, 8:03am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/2 "2020-09-16T08:03:36Z")
Hey @pankaj0172
U can follow this step on this post
> [@Using the xpack.encryptedSavedObjects.encryptionKey for Alerts and Actions in kibana 7.9](https://discuss.elastic.co/t/using-the-xpack-encryptedsavedobjects-encryptionkey-for-alerts-and-actions-in-kibana-7-9/248647):
>
> Hi, I'm using a docker compose file for ELK setup and using the latest 7.9 version for kibana. Now i want to set the xpack.encryptedSavedObjects.encryptionKey parameter in the kibana.yml so that i can use the alert and actions feature. how can i do/set it ? need some help on this
---
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 8:20am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/3 "2020-09-16T08:20:36Z")
Thanks, Where I can find or change my encryption key?
---
### Author:  [@Funky89](https://discuss.elastic.co/u/Funky89)
#### Post date: [September 16, 2020, 8:22am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/4 "2020-09-16T08:22:25Z")
You have to create one
> **[Strong Random Password Generator](https://passwordsgenerator.net/)**
---
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 8:29am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/5 "2020-09-16T08:29:26Z")
After making above changes, Now I'm not able start Kibana service. Any idea?
---
### Author:  [@Funky89](https://discuss.elastic.co/u/Funky89)
#### Post date: [September 16, 2020, 8:31am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/6 "2020-09-16T08:31:21Z")
Can you put the kibana.yml file?
---
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 8:33am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/7 "2020-09-16T08:33:32Z")
```
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601
# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "192.168.102.15"
# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""
# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false
# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576
# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"
# The URLs of the Elasticsearch instances to use for all your queries.
#elasticsearch.hosts: ["http://localhost:9200"]
# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true
# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"
# The default application to load.
#kibana.defaultAppId:"home"
#kibana.defaultAppId:"dashboard/3e976f602919ca6f3fb84109e93da9b7"
# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
elasticsearch.username: "kibana_system"
elasticsearch.password: "ElfgaStsic$$@20ts20"
# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: true
#server.ssl.certificate: /etc/letsencrypt/live/es.abc.com/fullchain.pem
#server.ssl.key: /etc/letsencrypt/live/es.abc.com/privatekey.pem
# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files are used to verify the identity of Kibana to Elasticsearch and are required when
#xpack.security.http.ssl.client_authentication in Elasticsearch is set to required.
#elasticsearch.ssl.certificate: /etc/letsencrypt/live/els.abc.com/fullchain.pem
#elasticsearch.ssl.key: /etc/letsencrypt/live/els.abc.com/fullchain.pem
# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/etc/letsencrypt/live/es.abc.com/fullchain.pem"]
# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full
# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500
# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000
# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]
# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}
# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 30000
# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000
# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
#elasticsearch.logQueries: false
# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid
# Enables you specify a file where Kibana stores log output.
#logging.dest: stdout
#logging.dest: /var/log/kibana.log
# Set the value of this setting to true to suppress all logging output.
#logging.silent: false
# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false
# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false
# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000
# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English - en , by default , Chinese - zh-CN .
#i18n.locale: "en"
#xpack.monitoring.enabled: false
xpack.security.enabled: true
#xpack.security.encryptionKey:true
xpack.security.session.idleTimeout: "30m"
xpack.encryptedSavedObjects.encryptionKey: "6$NychGrXrPC.N!q"
```
---
### Author:  [@Funky89](https://discuss.elastic.co/u/Funky89)
#### Post date: [September 16, 2020, 8:39am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/8 "2020-09-16T08:39:05Z")
> [@pankaj0172](#):
>
> `xpack.encryptedSavedObjects.encryptionKey: "6$NychGrXrPC.N!q"`
Wrong key, you need to make a 32 character key, not a 16 character key
here is an example
---
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 8:45am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/9 "2020-09-16T08:45:26Z")
> [@Funky89](#):
>
> u need to make a 32 chara
Thanks, It works but now it's showing below changes needs to be done. Please suggest
---
### Author:  [@Funky89](https://discuss.elastic.co/u/Funky89)
#### Post date: [September 16, 2020, 8:52am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/10 "2020-09-16T08:52:31Z")
You need to set up TLS security ( http to https )
Read this
> **[Encrypt communications in Kibana | Kibana Guide \[7.9\] | Elastic](https://www.elastic.co/guide/en/kibana/current/configuring-tls.html)**
---
### Author:  [@pankaj0172](https://discuss.elastic.co/u/pankaj0172)
#### Post date: [September 16, 2020, 9:04am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/11 "2020-09-16T09:04:44Z")
> [@Funky89](#):
>
> need to set up TLS security ( http to https )
Thanks Funky, I will look into it and get back to you. Thanks for your prompt response, really appreciated.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 14, 2020, 9:04am UTC](https://discuss.elastic.co/t/not-able-to-configure-alerts-in-kibana/248765/12 "2020-10-14T09:04:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.