Stack monitoring issues on single node cluster

Hi, trying to set up node monitoring with metricbeat on a single node cluster (i know its best practise to have a monitoring node but this is just for testing etc) i've followed the install and looking at the logs it appears to be capturing data however no indexes are being created and data is not reaching kibana but i can't see any errors in logs to suggest that its failing to reach/contact

below is what journalctl is showing me

Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.514Z        INFO        instance/beat.go:299        Setup Beat: metricbeat; Version: 7.9.3
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.514Z        INFO        [index-management]        idxmgmt/std.go:184        Set output.elasticsearch.index to 'metricbeat-7.9.3' as ILM is enabled.
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.515Z        INFO        eslegclient/connection.go:99        elasticsearch url: https://localhost:9200
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.515Z        INFO        [publisher]        pipeline/module.go:113        Beat name: bur-c1-n1
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.529Z        INFO        instance/beat.go:450        metricbeat start running.
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.529Z        INFO        [monitoring]        log/log.go:118        Starting metrics logging every 30s
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.530Z        INFO        cfgfile/reload.go:164        Config reloader started
Nov 11 12:03:45 metricbeat[23957]: 2020-11-11T12:03:45.530Z        INFO        cfgfile/reload.go:224        Loading of config files completed.
Nov 11 12:03:48 metricbeat[23957]: 2020-11-11T12:03:48.513Z        INFO        [add_cloud_metadata]        add_cloud_metadata/add_cloud_metadata.go:89        add_cloud_metadata: hosting provider type not detected.
Nov 11 12:04:15 metricbeat[23957]: 2020-11-11T12:04:15.531Z        INFO        [monitoring]        log/log.go:145        Non-zero metrics in the last 30s        {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":70,"time":{"ms":70}},"total":{"ticks":160,"time":{"ms":168},"value":160},"user":{"ticks":90,"time":{"ms":98}}},"handles":{"limit":{"hard":524288,"soft":1024},"open":8},"info":{"ephemeral_id":"d20d7e00-8757-4de4-a3b8-65a869b7032c","uptime":{"ms":30098}},"memstats":{"gc_next":15086880,"memory_alloc":13069152,"memory_total":28510040,"rss":77127680},"runtime":{"goroutines":19}},"libbeat":{"config":{"module":{"running":0},"reloads":1,"scans":1},"output":{"type":"elasticsearch"},"pipeline":{"clients":0,"events":{"active":0}}},"system":{"cpu":{"cores":8},"load":{"1":0,"15":0.02,"5":0.04,"norm":{"1":0,"15":0.0025,"5":0.005}}}}}}

This is my elasticsearch-xpack.yml

    module: elasticsearch
    xpack.enabled: true
    period: 10s
    hosts: ["https://localhost:9200"]
    username: "elastic"
    password: "************"
    ssl.enabled: true
    ssl.certificate: "/etc/elasticsearch/config/certs/fullchain.pem"
    ssl.key: "/etc/elasticsearch/config/certs/privkey.pem"
    ssl.verification_mode: "full"

and this is my metricbeat.yml

      output.elasticsearch:
      # Array of hosts to connect to.
      output.elasticsearch:
      hosts: ["https://localhost:9200"]

      # Protocol - either `http` (default) or `https`.
      protocol: "https"

      # Authentication credentials - either API key or username/password.
      #api_key: "id:api_key"
      username: "elastic"
      password: "************"

Hi,
Why do you use port 9300 ? It's usually use by elasticsearch for clustering purpose, by default API is exposed on 9200.
Do you have any logs in elasticsearch side ?
What's your logging level ?

Ah that was a typo from me trying different things, should be 9200
Logging level is debug and i cant see anything in the elasticsearch logs relating to it

What is the output from _cat/indices?v against Elasticsearch?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.