metricbeat

Read-only-port 10255 on Kubernetes node didn`t exist

谁都会走 提交于 2021-02-11 08:01:57
问题 I have a problem, I need to collect metric data from read-only-port located on 10255, but unfortunately by using netstat I found that such port don't exists at all. Can somebody help with advise, how could I create such port on kubelet or how can I avoid this port for data collection? 回答1: The kubelet requires a parameter to be set: --read-only-port=10255 (read more about kubelet) If you are using kubeadm to bootstrap the cluster, you can use a config file to pass in for the kubelet (look for

illegal_argument_exception: index.lifecycle.rollover_alias [metricbeat-6.8.4-alias] does not point to index [metricbeat-6.8.4-2020.02.24]

半城伤御伤魂 提交于 2020-08-05 17:25:07
问题 currently looking for help about setup ilm, i have setup the template, index alias and policy as below PUT metricbeat-6.8.4-alias-000001 { "aliases": { "metricbeat-6.8.4-alias": { "is_write_index": true } } } PUT _template/metricbeat-6.8.4-alias { "index_patterns": ["metricbeat-6.8.4-*"], "settings": { "number_of_shards": 1, "number_of_replicas": 1, "index.lifecycle.name": "Delete_Index", "index.lifecycle.rollover_alias": "metricbeat-6.8.4-alias" } } but still error ocurred like below illegal

How to set hostname in global service in Docker Swarm

夙愿已清 提交于 2020-07-19 04:26:19
问题 I have a service deployed to my Docker Swarm Cluster as global service (ELK Metricbeat). I want to each of this service to have a hostname the same as the hostname of the running node (host)? in another word, how I can achieve the same result in the yml file such as: docker run -h `hostname` elastic/metricbeat:5.4.1 this is my yml file: metricbeat: image: elastic/metricbeat:5.4.1 command: metricbeat -e -c /etc/metricbeat/metricbeat.yml -system.hostfs=/hostfs hostname: '`hostname`' volumes: -

How to connect metricbeat to elasticsearch and kibana with docker

◇◆丶佛笑我妖孽 提交于 2020-05-13 13:42:09
问题 I've setup elasticsearch and kibana with docker compose. elasticsearch is deployed on: localhost:9200 while kibana is deployed on localhost:5601 When trying to deploy metricbeat with docker run I got the following errors: $ docker run docker.elastic.co/beats/metricbeat:6.3.2 setup -E setup.kibana.host=kibana:5601 -E output.elasticsearch.hosts=["localhost:9200"] Exiting: Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch http://localhost

How to connect metricbeat to elasticsearch and kibana with docker

ぃ、小莉子 提交于 2020-05-13 13:41:46
问题 I've setup elasticsearch and kibana with docker compose. elasticsearch is deployed on: localhost:9200 while kibana is deployed on localhost:5601 When trying to deploy metricbeat with docker run I got the following errors: $ docker run docker.elastic.co/beats/metricbeat:6.3.2 setup -E setup.kibana.host=kibana:5601 -E output.elasticsearch.hosts=["localhost:9200"] Exiting: Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch http://localhost

How to connect metricbeat to elasticsearch and kibana with docker

可紊 提交于 2020-05-13 13:41:19
问题 I've setup elasticsearch and kibana with docker compose. elasticsearch is deployed on: localhost:9200 while kibana is deployed on localhost:5601 When trying to deploy metricbeat with docker run I got the following errors: $ docker run docker.elastic.co/beats/metricbeat:6.3.2 setup -E setup.kibana.host=kibana:5601 -E output.elasticsearch.hosts=["localhost:9200"] Exiting: Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch http://localhost

How can I parse custom Metricbeat dictionary for Kibana?

元气小坏坏 提交于 2019-12-23 04:47:07
问题 I have logstash set up sending to Kibana, and it tags each log file with two custom fields -- Cluster and Node: I would like to add the same two fields to my Metricbeat configuration using the "fields" option, but when I do this it comes through as a dictionary in Kibana: Here is the Metricbeat config file I'm using: metricbeat.modules: - module: system metricsets: # CPU stats - cpu # System Load stats - load # Per CPU core stats #- core # IO stats #- diskio # Per filesystem stats -