Once the set up is entire, the Elasticsearch assistance really should be enabled after which you can begun by making use of the subsequent commands:
Unzip the downloaded file into your directory you want to run from. This can be on exactly the same host because the as the Elasticsearch, Kibana or Logstash host you would like to interrogate, or with a distant server or workstation.
Just a checking export archive produced by the diagnostic utility is supported. It will not operate with a standard diagnostic bundle or even a customized archive.
It is going to undergo Each individual file line by line checking the information. For anyone who is only worried about IP addresses, you don't have to configure just about anything.
When operating the diagnostic from a workstation you may face troubles with HTTP proxies accustomed to shield interior equipment from the internet. In most cases you'll likely not require a lot more than a hostname/IP and a port.
If glitches manifest when attempting to acquire diagnostics from Elasticsearch nodes, Kibana, or Logstash processes running inside Docker containers, think about operating Using the --type set to api, logstash-api, or kibana-api to validate which the configuration will not be triggering challenges with the program connect with or log extraction modules within the diagnostic. This should enable the REST API subset to get properly gathered.
This tends to be completed For each and every discovered container within the host(not merely ones made up of Elasticsearch). In addition, when it is feasible to ascertain if the phone calls are legitimate, the Elasticsearch support utility can even make an effort to make the same old system phone calls to your host OS jogging the containers.
Or by the identical version quantity that produced the archive as long as It's really a supported version. Kibana and Logstash diagnostics are usually not supported at the moment, Whilst you might process All those making use of the single file by file functionality for every entry.
Much like Elasticsearch regional method, this runs in opposition to a logstash system jogging on the identical host as the installed diagnostic utility. Retrieves Logstash REST API dignostic information plus the output from the exact same program calls since the Elasticsearch sort. logstash-distant
At the time Elasticsearch is completed setting up, open its key configuration file with your favored textual content editor: /etc/elasticsearch/elasticsearch.yml
All configuration used by the utility is situated on the /config underneath the folder made once the diagnostic utility was unzipped. These might be modified to vary some behaviors during the diagnostic utility.
Queries a Kibana procedures working on another host compared to utility. Comparable to the Elasticsearch remote selection. Collects the same artifacts since the kibana-area choice. kibana-api
It truly is run by means of a separate execution script, and will method any valid Elasticsearch cluster diagnostic archive produced by Support Diagnostics 6.four or greater. It might also method only one file. It does not should be operate on the identical host that made the diagnostic.
Running the kibana-api variety to suppress procedure contact and log collection and explicitly configuring an output directory (This is certainly also the option that needs to be used when collecting the diagnostic for Kibana in Elastic Cloud).