Have a question? Want to report an issue? Contact JFrog support
Elasticsearch is packaged into the Mission Control installation. The following describes the different variations for each distribution package type:
| Distribution | Packaging |
|---|---|
| Docker | Elasticsearch for Docker is added as a Docker container to the Mission Control docker-compose project. This installs version 5.5.2. |
Debian | Elasticsearch 5.6.2 is included in the Mission Control Debian project. Linux service files are added. |
| RPM | Elasticsearch 5.6.2 is included in the Mission Control RPM project. Linux service files are added. |
After Mission Control is fully installed, the Elasticsearch data files can be found in the following locations:
| File | Location |
|---|---|
| Binaries | <JMFC_HOME>/elasticsearch/ |
| Data files | Linux: <JMFC_HOME>/elasticsearch/ Docker: <JMFC_HOME>/elasticsearch/ |
Elasticsearch uses the following communication ports:
| Service | Port |
|---|---|
| HTTP API | 9200 |
Java Client | 9300 |
There are two aliases to store and retrieve data:
| Alias Name | Description |
|---|---|
| active_insight_data | Used point to active index to push data. |
| search_insight_data | Used to search and retrieve data |
On installation, these aliases and indices of format active_insight_data_timestamp* are created.
Mission Control is pre-configured to periodically cleanup indexes to keep data for a period of one year.