elastic-stack

问题 I have hosted a shared elasticsearch index (IP Restricted though using GCP Firewall) but I want to add any kind of security on this Index so that others can do any operations freely as they are doing now without any notice but dont want to allow anybody except (having auth) to delete the entire Index. My ElasticSearch details: { "name" : "node-1", "cluster_name" : "production", "cluster_uuid" : "<hash>", "version" : { "number" : "7.1.1", "build_flavor" : "default", "build_type" : "tar",

问题 I have a dockerized application with a few services running using docker-compose. I'd like to connect this application with ElasticSearch/Logstash/Kibana (ELK) using another docker-compose application, docker-elk. Both of them are running in the same docker machine in development. In production, that will probably not be the case. How can I configure my application's docker-compose.yml to link to the ELK stack? 回答1: Update Jun 2016 The answer below is outdated starting with docker 1.10. See

问题 I have a dockerized application with a few services running using docker-compose. I'd like to connect this application with ElasticSearch/Logstash/Kibana (ELK) using another docker-compose application, docker-elk. Both of them are running in the same docker machine in development. In production, that will probably not be the case. How can I configure my application's docker-compose.yml to link to the ELK stack? 回答1: Update Jun 2016 The answer below is outdated starting with docker 1.10. See

问题 I want to implement autocomplete feature in ES I have followed this tutorial from ES documentations my Indexing is: { "properties" : { "suggest" : { "type" : "completion" }, "titleKeyword" : { "type": "keyword" } } } } I am putting text value in titleKeyword field then I queried like follows { "suggest" : { "my-suggestion" : { "text" : "iphone", "term" : { "field" : "titleKeyword" } } } } The result is: ... "suggest": { "my-suggestion": [ { "text": "iphone", "offset": 0, "length": 6, "options

问题 I want to implement autocomplete feature in ES I have followed this tutorial from ES documentations my Indexing is: { "properties" : { "suggest" : { "type" : "completion" }, "titleKeyword" : { "type": "keyword" } } } } I am putting text value in titleKeyword field then I queried like follows { "suggest" : { "my-suggestion" : { "text" : "iphone", "term" : { "field" : "titleKeyword" } } } } The result is: ... "suggest": { "my-suggestion": [ { "text": "iphone", "offset": 0, "length": 6, "options

问题 I want to implement autocomplete feature in ES I have followed this tutorial from ES documentations my Indexing is: { "properties" : { "suggest" : { "type" : "completion" }, "titleKeyword" : { "type": "keyword" } } } } I am putting text value in titleKeyword field then I queried like follows { "suggest" : { "my-suggestion" : { "text" : "iphone", "term" : { "field" : "titleKeyword" } } } } The result is: ... "suggest": { "my-suggestion": [ { "text": "iphone", "offset": 0, "length": 6, "options

问题 I want to implement autocomplete feature in ES I have followed this tutorial from ES documentations my Indexing is: { "properties" : { "suggest" : { "type" : "completion" }, "titleKeyword" : { "type": "keyword" } } } } I am putting text value in titleKeyword field then I queried like follows { "suggest" : { "my-suggestion" : { "text" : "iphone", "term" : { "field" : "titleKeyword" } } } } The result is: ... "suggest": { "my-suggestion": [ { "text": "iphone", "offset": 0, "length": 6, "options

问题 I am already running ELK stack with Elasticsearch(ES) 1.7 with docker container with 3 nodes, each running one ES container, running behind nginx server. Now I am trying to upgrade ES to 2.4.0. Root user is not allowed in ES 2.4.0 so I am using -Des.root.insecure.allow=true option. #Pulling SLES12 thin base image FROM private-registry-1 #Author MAINTAINER xyz # Pre-requisite - Adding repositories RUN zypper ar private-registry-2 RUN zypper --no-gpg-checks -n refresh #Install required packages

问题 Running mvn clean install pulls up this error( Windows) [ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.20.1:start (prepare-environment) on project integration-test: Execution prepare-environment of goal io.fabric8:docker-maven-plugin:0.20.1:start failed: Start-Job failed with unexpected exception: [sebp/elk:latest] "elk": Timeout after 120365 ms while waiting on url http://localhost:32774/ 来源： https://stackoverflow.com/questions/44226315/failed-to-execute-fabric8-docker

问题 is there a way to choose if I want to have a logback appender or not, via environment variable? I have a dockerized spring boot Microservice and added now the ELK stack. That works fine so far. But now if I want to start my service without ELK stack, the application throws an error, that it doesn't know the host of Logstash: app | 10:09:23,537 |-ERROR in ch.qos.logback.classic.net.SyslogAppender[SYSLOG] - Could not create SyslogWriter java.net.UnknownHostException: logstash: Name or service