Schedule Report - kibana.configuration trouble

Elastic Stack Kibana
1

Hi all,

I have Elastic Stack version 8.19. Is it possible to schedule report sending without using watchers or URLs?
We tried configuring this in kibana.yml:

Kibana Email settings

xpack.actions.preconfigured:
my-email:
name: preconfigured-email-connector-type
actionTypeId: .email
config:
service: ses
from: xxxxx@aaaa.it
host: email-smtp.eu-west-1.amazonaws.com
port: 587
secure: true
hasAuth: true
secrets:
user: **************
password:*************

notifications.connectors.default.email: my-email

But kibana doesn't start and we can't find any relevant errors in kibana.log.

2

Hello @Cristina_Marletta_Li

As per the below documentation it can be done via script as well :

As per the information shared i see you are using service as ses :

Could you please review the configuration once, also if Kibana is not starting there should be some logs which could help to find the exact cause & correct the configuration in kibana.yml

Thanks!!

3

Hi Tortoise, thanks.

It works now (I'm copying the working configuration below, although the formatting has been lost in the copy). Oddly enough, however, for it to work, we had to set
. service: other
. hasAuth: true

even though the documentation states:
. service: ses
. hasAuth: false (if the password is stored in kibana.keystore)

xpack.actions.preconfigured:
my-email:
name: preconfigured-email-connector-type
actionTypeId: .email
config:
service: other
from: ********@********.it
host: email-smtp.eu-west-1.amazonaws.com
port:  465
secure: true
hasAuth: true
secrets:
user: ************

notifications.connectors.default.email: my-email

We can't explain this behavior.

2 Likes
4

Thank you for posting what worked for you; it really helped us out. We were having issues getting report e-mails to work, and calling out the connector in the config worked (the docs call it something else, but it causes Kibana to fail to load).

notifications.connectors.default.email