java毕业设计 基于SpringCloud+Vue前后端分离的商城类网站源码+详细文档+全部资料（优秀项目）.zip

# Elastic stack (ELK) on Docker [](https://www.elastic.co/blog/category/releases) [](https://github.com/deviantony/docker-elk/actions?query=workflow%3ACI+branch%3Amaster) [](https://gitter.im/deviantony/docker-elk?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) Run the latest version of the [Elastic stack][elk-stack] with Docker and Docker Compose. It gives you the ability to analyze any data set by using the searching/aggregation capabilities of Elasticsearch and the visualization power of Kibana. *:information_source: The Docker images backing this stack include [X-Pack][xpack] with [paid features][paid-features] enabled by default (see [How to disable paid features](#how-to-disable-paid-features) to disable them). **The [trial license][trial-license] is valid for 30 days**. After this license expires, you can continue using the free features seamlessly, without losing any data.* Based on the official Docker images from Elastic: * [Elasticsearch](https://github.com/elastic/elasticsearch/tree/master/distribution/docker) * [Logstash](https://github.com/elastic/logstash/tree/master/docker) * [Kibana](https://github.com/elastic/kibana/tree/master/src/dev/build/tasks/os_packages/docker_generator) Other available stack variants: * [`tls`](https://github.com/deviantony/docker-elk/tree/tls): TLS encryption enabled in Elasticsearch. _Regularly rebased onto `master`_ * [`searchguard`](https://github.com/deviantony/docker-elk/tree/searchguard): Search Guard support --- ## Philosophy We aim at providing the simplest possible entry into the Elastic stack for anybody who feels like experimenting with this powerful combo of technologies. This project's default configuration is purposely minimal and unopinionated. It does not rely on any external dependency or custom automation to get things up and running. Instead, we believe in good documentation so that you can use this repository as a template, tweak it, and make it _your own_. [sherifabdlnaby/elastdocker][elastdocker] is one example among others of project that builds upon this idea. --- ## Contents 1. [Requirements](#requirements) * [Host setup](#host-setup) * [SELinux](#selinux) * [Docker for Desktop](#docker-for-desktop) * [Windows](#windows) * [macOS](#macos) 1. [Usage](#usage) * [Version selection](#version-selection) * [Bringing up the stack](#bringing-up-the-stack) * [Cleanup](#cleanup) * [Initial setup](#initial-setup) * [Setting up user authentication](#setting-up-user-authentication) * [Injecting data](#injecting-data) * [Default Kibana index pattern creation](#default-kibana-index-pattern-creation) 1. [Configuration](#configuration) * [How to configure Elasticsearch](#how-to-configure-elasticsearch) * [How to configure Kibana](#how-to-configure-kibana) * [How to configure Logstash](#how-to-configure-logstash) * [How to disable paid features](#how-to-disable-paid-features) * [How to scale out the Elasticsearch cluster](#how-to-scale-out-the-elasticsearch-cluster) * [How to reset a password programmatically](#how-to-reset-a-password-programmatically) 1. [Extensibility](#extensibility) * [How to add plugins](#how-to-add-plugins) * [How to enable the provided extensions](#how-to-enable-the-provided-extensions) 1. [JVM tuning](#jvm-tuning) * [How to specify the amount of memory used by a service](#how-to-specify-the-amount-of-memory-used-by-a-service) * [How to enable a remote JMX connection to a service](#how-to-enable-a-remote-jmx-connection-to-a-service) 1. [Going further](#going-further) * [Plugins and integrations](#plugins-and-integrations) * [Swarm mode](#swarm-mode) ## Requirements ### Host setup * [Docker Engine](https://docs.docker.com/install/) version **17.05** or newer * [Docker Compose](https://docs.docker.com/compose/install/) version **1.20.0** or newer * 1.5 GB of RAM *:information_source: Especially on Linux, make sure your user has the [required permissions][linux-postinstall] to interact with the Docker daemon.* By default, the stack exposes the following ports: * 5044: Logstash Beats input * 5000: Logstash TCP input * 9600: Logstash monitoring API * 9200: Elasticsearch HTTP * 9300: Elasticsearch TCP transport * 5601: Kibana **:warning: Elasticsearch's [bootstrap checks][booststap-checks] were purposely disabled to facilitate the setup of the Elastic stack in development environments. For production setups, we recommend users to set up their host according to the instructions from the Elasticsearch documentation: [Important System Configuration][es-sys-config].** ### SELinux On distributions which have SELinux enabled out-of-the-box you will need to either re-context the files or set SELinux into Permissive mode in order for docker-elk to start properly. For example on Redhat and CentOS, the following will apply the proper context: ```console $ chcon -R system_u:object_r:admin_home_t:s0 docker-elk/ ``` ### Docker for Desktop #### Windows Ensure the [Shared Drives][win-shareddrives] feature is enabled for the `C:` drive. #### macOS The default Docker for Mac configuration allows mounting files from `/Users/`, `/Volumes/`, `/private/`, and `/tmp` exclusively. Make sure the repository is cloned in one of those locations or follow the instructions from the [documentation][mac-mounts] to add more locations. ## Usage ### Version selection This repository tries to stay aligned with the latest version of the Elastic stack. The `master` branch tracks the current major version (7.x). To use a different version of the core Elastic components, simply change the version number inside the `.env` file. If you are upgrading an existing stack, please carefully read the note in the next section. **:warning: Always pay attention to the [official upgrade instructions][upgrade] for each individual component before performing a stack upgrade.** Older major versions are also supported on separate branches: * [`release-6.x`](https://github.com/deviantony/docker-elk/tree/release-6.x): 6.x series * [`release-5.x`](https://github.com/deviantony/docker-elk/tree/release-5.x): 5.x series (End-Of-Life) ### Bringing up the stack Clone this repository onto the Docker host that will run the stack, then start services locally using Docker Compose: ```console $ docker-compose up ``` You can also run all services in the background (detached mode) by adding the `-d` flag to the above command. **:warning: You must rebuild the stack images with `docker-compose build` whenever you switch branch or update the version of an already existing stack.** If you are starting the stack for the very first time, please read the section below attentively. ### Cleanup Elasticsearch data is persisted inside a volume by default. In order to entirely shutdown the stack and remove all persisted data, use the following Docker Compose command: ```console $ docker-compose down -v ``` ## Initial setup ### Setting up user authentication *:information_source: Refer to [How to disable paid features](#how-to-disable-paid-features) to disable authentication.* The stack is pre-configured with the following **privileged** bootstrap user: * user: *elastic* * password: *changeme* Although all stack components work out-of-the-box with this user, we strongly recommend using the unprivileged [built-in users][builtin-users] instead for increased security. 1. Initialize passwords for built-in users ```console $ docker-compose exec -T elasticsearch bin/elasticsearch-setup-passwords auto --batch ``` Passwords for all 6 built-in users will be randomly generated. Take note of th