I'm trying to setup heartbeat.7.5.2 and able to do so; could find the HTTP/ TCP end-points status on Kibana (under 'Uptime'). However, it doesnt show up the name/status/url; despite i've explicitly added 'name & id' in the tcp.yml.
Ex:
type: tcp # monitor type tcp. Connect via TCP and optionally verify endpoint
schedule: '@every 5s' # every 5 seconds from start of beat
hosts: ["myad.domain.com"]
name: 'ad-service'
id: 'ad-service'
ports: [636]
ipv4: true
mode: any
I expect 'ad-service' be listed in the uptime console, but it just shows the pie-chart/histogram as 1/1.
Can I know what's missing that name/id are listed under 'monitor status' in the same console ?
Yes, I could see data flowing in and able to search it in index. Moreover, as you could see the uptime reports the monitors as "3", but just that it doesn't list under "monitor status"
I'm not doing any query, as you notice in the Uptime-UI, I'm finding only the monitors reported as numbers, but not listing the names (generally it should, but I'm assuming something is missing in heartbeat config)
Same is what I have, just that I'm using monitors.d instead of heartbeat.yml (to avoid frequent service restart).
Moreover, I don't have any processors, especially geo/cloud-meta; which I don't require. Besides, by default I could search the common values (ex: monitor.status, monitor.name) in the index, but not listing as shown in the pic.
Hello @sivaaws Can you go to dev tool and do query like this, and send me result back, it will help me determine, what kind of docs are coming into es, and whether there are any fields missing. Also try increasing monitor schedule to perhaps 60s, and see if that resolves the issue.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.