The file: diagnostic.log file will be generated and included in the archive. In all however the worst scenario an archive is going to be produced. Some messages are going to be prepared on the console output but granualar mistakes and stack traces will only be penned to this log.

There are a number of options for interacting with purposes running in just Docker containers. The easiest way to operate the diagnostic is just to accomplish a docker run -it which opens a pseudo TTY.

For those who contact us by email, you should use the email tackle that you registered with, so that we can help you extra quickly.

If you have a message expressing that it may't locate the diagnostic node, it always indicates you might be functioning the diagnostic on a number made up of a different node in comparison to the a person you happen to be pointing to. Attempt jogging in distant node or shifting the host that you are executing on.

Including logging-cluster-05-01 and logging cluster 05-08. You may as well override the actual checking index name applied if that helps in handling different imports. Regardless of what worth you utilize is going to be appended to .monitoring-es-7-. If you do not specify this parameter, the imported facts might be indexed in the typical monitoring index title format with the current date appended. No spaces during the cluster or index names are allowed.

If you have an set up exactly where there is a 3rd party ssh/sftp server working on Home windows and so are open up to sharing facts of the set up Be at liberty to open a ticket for future support.

Functioning the api type to suppress technique get in touch with and log assortment and explicitly configuring an output Listing.

directory during the diagnostic distribution you can find a sample script named diagnostic-container-exec.sh which contains an example of how To accomplish this.

The hostname or IP deal with from the target node. Defaults to localhost. IP tackle will frequently deliver Elasticsearch support the most dependable effects.

Crafting output from the diagnostic zip file for the Doing work directory Along with the staff decided dynamically:

This makes sure you can differentiate in between occurrences of discrete nodes from the cluster. In the event you swap all of the IP addresses with a world XXX.XXX.XXX.XXX mask you will get rid of the ability to see which node did what.

When you are within a hurry and don't head dealing with a Q&A process it is possible to execute the diagnostic without having choices. It can then enter interactive mode and stroll you thru the entire process of executing with the right options. Merely execute ./diagnostics.

Generates obfuscated prompt to the elasticsearch password. Passing of a plain textual content password for automatic processes is achievable although not inspired given it can not be hid through the historical past.

Be sure to have a valid Java set up that the JAVA_HOME surroundings variable is pointing to.