xpack | Experimental compression format

Only thing I can think of while seeing this code is that the value of power is huge:

Your issue looks similar to another issue, see here: Certificate for doesn't match any of the subject alternative names

So I would assume that if you add the SAN extension localhost as DNS and the ip address of localhost to the elasticsearch certificate it should work. So adding the following additional parameters: --dns localhost --ip 127.0. 0.1. Can you give the command below a try and share your results here?

This apm rollover policies are created by default when using apm and these policies uses the default user 'kibana' to create it.. So Kibana user dont have access for update.

So as per documentation line if I modify the default apm rollover policy with the logged in user[having access for update ilm],then select the 'retry index' option has solved this error.

Documentation: If you use Elasticsearch’s security features, ILM performs operations as the user who last updated the policy. ILM only has the roles assigned to the user at the time of the last policy update.

For the sake of completeness, I want to subsume at least the part of the solutions given by @axelclk and @IanGabes that worked. First of all, it seemed to be necessary to manually add all implicit dependencies plus the repositories they originate from to server's build.gradle, corresponding to the pom.xml files of matheclipse-core and of matheclipse-external:

If anyone comes across this problem in the future, make sure your ingress is properly configured. The error message suggests that its a misconfiguration with the ingress.

Above configurations are fine, what you need to do is generate node certificates in order to encrypt the elasticsearch internode communication(TLS - Transport Layer Security). The reason is, by default elasticsearch transfer data in text format(even passwords) which is a poor security practice. Therefore, inter-node communication should be encrypted before enabling Xpack security. This can be achieved by using elasticsearch certutil package. Follow the below steps(not suitable for production only for testing purposes).

1. Go to elasticsearch 'bin' directory in your terminal.
2. Execute command ./elasticsearch-certutil ca This will generate a certificate authority in your elasticsearch main directory. When you are asked to enter a filename for your CA, hit "enter" then it'll take the default filename 'elastic-stack-ca.p12'. Then after it'll ask for a password for the CA(Certificate Authority), then again hit "enter".
3. Now we need to generate a TLS certificate for your elasticsearch instance using above generated CA file. For that, execute ./elasticsearch-certutil cert --ca elastic-stack-ca.p12. when executing this command first, it'll ask for the password of your CA file, then hit 'enter' then after it'll ask for TLS certificate name then again hit 'enter' then it'll take the TLS certificate name as 'elastic-certificates.p12' which is the default name finally it'll ask for a password for the TLS certificate, then again hit 'enter'. Now you will be able see a two new files in your elasticsearch main directory.
4. Copy the elastic-certificates.p12 file into elasticsearch 'config' directory. If you have multiple elasticsearch nodes copy the same file into each node's 'config' directory.
5. Now start the elasticsearch instance/s

Please note that above configuration steps are not suitable for production, only for testing... :)

There are several problems in your setup:

• You don't add the package for Kafka support as described in docs. It's either needs to be added when starting pyspark, or when initializing session, something like this (change 3.0.1 to version that is used in your jupyter container):

If transmitting via logstash works in general, add a filter block as Val proposed in the comments and use this json plugin/filter: elastic.co/guide/en/logstash/current/plugins-filters-json.html - it automatically parses the json into elasticsearch fields

So it took me some time, but I've figured out what was the problem with my certificate. I didn't add it to the trusted root store on my windows machine.

In the end I've created a Winlogbeat crt and key using the elasticsearch-certutil tool by adding a Winlogbeat instance to the instances.yml file and copied the winlogbeat.crt, winlogbeat.key and ca.crt to my windows machine.

Note - You can find all of them under /var/lib/docker/volumes/es_certs/_data/

On the windows machine I configured the Winlogbeat the normal way and in the end I've added the ca.crt to the trusted root store using this tutorial.