So, I have created a brand new deployment on cloud.elastic.co. Created an alert on it with an email action. It goes correclty from PENDING to ACTIVE or OK.
Now, I create a deployment with several kibanas that are connected to the same cluster. So on this cluster I have:
- the cloud kibana that is delivered along with the elastic.co service (with the bizarre and long URL)
some other kibana that I host (nice domain names and own
Here is the configuration of my own kibanas
server.basePath: "/bigdata" server.rewriteBasePath: false kibana.index: .kibana-XXX elasticsearch.hosts: ["https://XXXXXXXXXXXXX12baa1dc4.eu-west-1.aws.found.io:9243"] elasticsearch.username: "kibanaXXX-" elasticsearch.password: "XXXXXXX" logging.dest: /home/XXX/logs/kibana.log xpack.reporting.encryptionKey: "znUXXXXQEoiveBYh" xpack.reporting.kibanaServer.port: 443 xpack.reporting.kibanaServer.protocol: https xpack.reporting.kibanaServer.hostname: XXX.flightwatching.com xpack.reporting.index: ".reporting-XXX_" xpack.encryptedSavedObjects.encryptionKey: "znUxbvXXXXXXXnUxbvCDuQEoiveBYh" xpack.security.encryptionKey: "znUxbvXXXXXXXnUxbvCDuQEoiveBYh"
Well, in that case (multiple instances), it seems that the alerting does not work. The alerts remain PENDING, even if it seemed that it workd 1 time, randomly
It remembers me this issue with reporting, that is similar.
anybody to check/validate/fix?