# Kibana@Docker new instances occure in stack monitoring when I reboot the Kibana node **URL:** \ **Category:** Kibana\ **Created:** [December 15, 2020, 10:18am UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697 "2020-12-15T10:18:03Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Waxman](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@Waxman](https://discuss.elastic.co/u/Waxman)\ **Post date:** [December 15, 2020, 10:18am UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697/1 "2020-12-15T10:18:03Z")
Hi There, I'm running on elk 7.9.2 with two kibana's nodes. I'm noticing some interesting behaviour in the stack monitoring ![kibana_mirror](https://us1.discourse-cdn.com/elastic/original/3X/c/e/ce8720c13710149a5a7708de01a14df4694014e6.png) ![mon1](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c72458d48cb997b37085625ced1cf1ac4cb88fc3.png) ![mon2](https://us1.discourse-cdn.com/elastic/original/3X/9/f/9f605d4f74861d16f65138509075d89ba415a0d8.png) . When I reboot one of two kibana's node then I've lost my monitoring graphs and I start from the beginning (see snapshots) Is this because I haven't linked some persisten volume ? See my kibana.yml and docker-compose.yml (they are same for both nodes) kibana.yml ```auto server.port: 5601 server.host: "0.0.0.0" server.name: "kib01d" elasticsearch.hosts: ["https://xxx:9200","https://xxx:9200","https://xxx:9200"] server.ssl.enabled: true elasticsearch.username: "kibana_system" elasticsearch.password: "xxx" server.ssl.certificate: /usr/share/kibana/config/certs/xxx.crt server.ssl.key: /usr/share/kibana/config/certs/xxx.key elasticsearch.ssl.certificateAuthorities: ["/usr/share/kibana/config/certs/ca/ca.crt"] elasticsearch.ssl.verificationMode: certificate pid.file: /usr/share/kibana/kibana.pid logging.verbose: true logging.dest: /usr/share/kibana/logs/kibana.log xpack.security.encryptionKey: "xxx" xpack.encryptedSavedObjects.encryptionKey: "xxx" #xpack.monitoring.collection.enabled: true xpack.ml.enabled: true telemetry.enabled: false ``` docker-compose.yml: ```auto version: '3' services: kib01d: image: /elk/kibana/kibana:7.9.2 container_name: kib01d environment: - bootstrap.memory_lock=true - publish-all - ES_JAVA_OPTS="-Xms16G -Xmx16G" ulimits: memlock: soft: -1 hard: -1 volumes: - /srv/Docker/config:/usr/share/kibana/config - /srv/Docker/logs:/usr/share/kibana/logs dns: dns_search: xxx.xx ports: - 5601:5601 network_mode: "host" metricbeats: image: harbor.upc.pl/elk/beats/metricbeat:7.9.2 container_name: metricbeat05 environment: - publish-all user: root depends_on: - kib01d command: metricbeat -e -E name=MB_Kibana_1 volumes: - "/srv/Docker/metricbeat/metricbeat.yml:/usr/share/metricbeat/metricbeat.yml:ro" - "/var/run/docker.sock:/var/run/docker.sock:ro" - "/srv/Docker/metricbeat/modules.d:/usr/share/metricbeat/modules.d" - "/sys/fs/cgroup:/hostfs/sys/fs/cgroup:ro" - "/proc:/hostfs/proc:ro" - "/:/hostfs:ro" - "/srv/Docker/config:/usr/share/kibana/config" ``` Any ideas ? ---
**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\ **Post date:** [December 17, 2020, 1:35pm UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697/2 "2020-12-17T13:35:48Z")
> [@Waxman](#): > > Is this because I haven't linked some persisten volume ? Monitoring data are written to the Elasticsearch. I don't see it in the provided `docker-compose.yml` file. How do you configure it? Does the `elasticsearch` docker configuration define `volumes` to persist data across restarts? ---
**Author:** ![Waxman](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@Waxman](https://discuss.elastic.co/u/Waxman)\ **Post date:** [December 30, 2020, 1:38pm UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697/3 "2020-12-30T13:38:28Z")
If you ask about how does metricbeat send the monitoring data to ELK, here you have a part of the metricbeat.yml: ```auto #========================== Elasticsearch output =============================== output.elasticsearch: hosts: ["https://x:9200", "https://xxl:9200", "https://xxx:9200"] username: "elastic" password: "xxx" ssl.verification_mode: "full" ssl.certificate_authorities: /usr/share/kibana/config/certs/ca/ca.crt ``` ---
**Author:** ![Waxman](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@Waxman](https://discuss.elastic.co/u/Waxman)\ **Post date:** [January 7, 2021, 1:29pm UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697/4 "2021-01-07T13:29:14Z")
Allright Folks, I know what happened there. Two things acctually: 1. I used docker-compose down & up (it's removing the container and create the new UUID) 2. I didn't create any persistent volume for keeping /usr/share/kibana/data When 2) was done then 1) disappeared even when I use command docker-compose down/up ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 4, 2021, 1:29pm UTC](https://discuss.elastic.co/t/kibana-docker-new-instances-occure-in-stack-monitoring-when-i-reboot-the-kibana-node/258697/5 "2021-02-04T13:29:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.