kibana-4

Elasticsearch: Merge result of aggregation by bucket key

由 ≡放荡痞女 提交于 2019-12-11 06:15:45
问题 I've indexed entities in Elasticsearch, which occur in my documents. The mapping for the entities looks like the following: "Entities": { "properties": { "EntFrequency": { "type": "long" }, "EntId": { "type": "long" }, "EntType": { "type": "string", "analyzer": "english", "fields": { "raw": { "type": "string", "index": "not_analyzed" } } }, "Entname": { "type": "string", "analyzer": "english", "fields": { "raw": { "type": "string", "index": "not_analyzed" } } } } }, [...] Furthermore, I use

Elasticsearch 2.2 : Cant install marvel plugin

由 隐身守侯 提交于 2019-12-11 00:43:10
问题 I am trying to install the marvel sense plugin for ES and Kibana on windows. I have ES version 2.2.0 and Kibana version 4.4.0 Here is what i tried to do For ES plugin install license i get -> Installing license... Trying https://download.elastic.co/elasticsearch/release/org/elasticsearch/plugi n/license/2.2.0/license-2.2.0.zip ... ERROR: failed to download out of all possible locations..., use --verbose to get detailed information i also tried plugin install marvel-agent but i get ->

Kibana4 to listen on Port 80 instead of Port 5601

由 僤鯓⒐⒋嵵緔 提交于 2019-12-10 11:18:19
问题 I have elasticsearch 1.4 and kibana4 running on an Amazo EC2 instance running RHEL7. Kibana4 is running as a standalone process and is not deployed in a web container such as nginx.It is listening on Port 5601.(the default port). I would like to have kibana listen on port 80. Can this be achieved without using nginx? If yes how? 回答1: Edit file {kibana-directory}/config/kibana.yml. Find this line: port: 5601 and change it to: port: 80 回答2: Full settings here: https://www.elastic.co/guide/en

Kibana is not connecting with elasticsearch shield SSL

由 喜你入骨 提交于 2019-12-10 10:34:49
问题 We are try to set up the shield SSL in local machine. Elasticsearch version : 2.2.1 Kibana version : 4.4.1 Shield version : Latest version We generated self signed crt, key, pem file as below: openssl req -out CSR.csr -new -newkey rsa:2048 -nodes -keyout privateKey.key openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout privateKey.key -out certificate.crt openssl req -out CSR.csr -key privateKey.key -new openssl x509 -x509toreq -in certificate.crt -out CSR.csr -signkey

ElasticSearch entered “read only” mode, node cannot be altered

由 筅森魡賤 提交于 2019-12-08 17:38:04
问题 Something happened during the night to my ES cluster (composed of 5 data nodes, 3 master nodes). To be honest, I have no idea what happened but all the indices and data were deleted and the cluster entered a "read only" mode, possibly hacked? When trying to get Kiban running i get the following: Tried restarting kibana - it restarted, nothing changed. Tried restarting Elastic - it restarted (all nodes), nothing changed. I then had a look at the cluster settings and this is what I got: {

How to do a time range search in Kibana

由 这一生的挚爱 提交于 2019-12-08 15:17:18
问题 We are using the ELK for log aggregation. Is it possible to search for events that occured during a particular time range. Lets say I want to see all exceptions that occurred between 10am and 11am in last month. Is it possible to extract the time part from @timestamp and do a range search on that somehow (similiar to date() in SQL)? 回答1: Thanks to Magnus who pointed me to looking at scripted fields. Take a look at: https://www.elastic.co/blog/kibana-4-beta-3-now-more-filtery or https://www

Can't run ./bin/kibana on ubuntu 14

由 假装没事ソ 提交于 2019-12-08 06:48:10
问题 I try to install Kibana 4 on Ubuntu 14.10 but whe i run ./bin/kibana, I have many error : ./../node/bin/node: 1: ./../node/bin/node:ELF: not found ./../node/bin/node: 2: ./../node/bin/node: W: not found ./../node/bin/node: 2: ./../node/bin/node: -NE: not found ./../node/bin/node: 4: ./../node/bin/node: Syntax error: "(" unexpected Java 8, Elasticsearch and nodejs are installed, Can you help me please ? Thanks. 回答1: This problem occurs if the wrong architecture is used. E.g. I first downloaded

Kibana4 to listen on Port 80 instead of Port 5601

由 淺唱寂寞╮ 提交于 2019-12-06 07:00:55
I have elasticsearch 1.4 and kibana4 running on an Amazo EC2 instance running RHEL7. Kibana4 is running as a standalone process and is not deployed in a web container such as nginx.It is listening on Port 5601.(the default port). I would like to have kibana listen on port 80. Can this be achieved without using nginx? If yes how? Edit file {kibana-directory}/config/kibana.yml. Find this line: port: 5601 and change it to: port: 80 Full settings here: https://www.elastic.co/guide/en/kibana/current/settings.html This should be added to config/kibana.yml server.port: 80 And run kibana server with

how to automate the configuration of an index pattern in kibana

由 为君一笑 提交于 2019-12-06 05:38:42
问题 Is it possible to automate the configuration of an index pattern in kibana? Either via some settings file or perhaps a rest api. After installation it's possible to do it manually. 回答1: Kibana 5.x exposes such an API to manage index patterns. To create index pattern one can issue below command to kibana access url (just edit the kibana endpoint, index-name and timestamp variables to match your needs): curl <kibana-endpoint>/es_admin/.kibana/index-pattern/<index-name>/_create\ -H "Content-Type

Missing data when using unique count and creating an aggregation in Kibana

由 限于喜欢 提交于 2019-12-06 02:34:15
问题 I have a behavior in Kibana, I can't explain. The following is a simple bar chart, counting unique users, filtered by application and a role, and ensuring certain fields exist on the logs: This graph shows that I have approx. 170 users which have the role 'Landmand'. If I split the bar by the term 'fields.Role', I would expect a identical chart, since I already applied a filter specifying 'fields.Role:Landmand' in the search. However I see this. This suddenly limits the unique count to approx
订阅 kibana-4