-
|
I have managed to get fping working but would like to have vsphere working as well. I did setup the go.d/vsphere.conf as
and my log from go.d.plugin -d -m vsphere
the only issue that sticks out to me is the warning unknown file format: '/etc/netdata/go.d/vshere.conf if anyone can point me in the right direction as to what to try next would be greatly appreciated |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
Hi, @Trash7276. Can you post here the content of |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ilyam8 # netdata go.d.plugin configuration for vsphere
#
# This file is in YAML format. Generally the format is:
#
# name: value
#
# There are 2 sections:
# - GLOBAL
# - JOBS
#
#
# [ GLOBAL ]
# These variables set the defaults for all JOBs, however each JOB may define its own, overriding the defaults.
#
# The GLOBAL section format:
# param1: value1
# param2: value2
#
# Currently supported global parameters:
# - update_every
# Data collection frequency in seconds. Default: 20.
#
# - autodetection_retry
# Re-check interval in seconds. Attempts to start the job are made once every interval.
# Zero means not to schedule re-check. Default: 0.
#
# - priority
# Priority is the relative priority of the charts as rendered on the web page,
# lower numbers make the charts appear before the ones with higher numbers. Default: 70000.
#
#
# [ JOBS ]
# JOBS allow you to collect values from multiple sources.
# Each source will have its own set of charts.
#
# IMPORTANT:
# - Parameter 'name' is mandatory.
# - Jobs with the same name are mutually exclusive. Only one of them will be allowed running at any time.
#
# This allows autodetection to try several alternatives and pick the one that works.
# Any number of jobs is supported.
#
# The JOBS section format:
#
# jobs:
#
# - name: job2
# param1: value1
# param2: value2
#
# - name: job2
# param1: value1
#
#
# [ List of JOB specific parameters ]:
# - url
# Server URL.
# Syntax:
# url: http://localhost:80
#
# - username
# Username for authentication.
# Syntax:
# username: tony
#
# - password
# Password for authentication.
# Syntax:
# password: stark
#
# - timeout
# HTTP response timeout.
# Syntax:
# timeout: 20
#
# - discovery_interval
# Module will rediscover new hosts and vms every interval.
# Syntax:
# discovery_interval: 300
#
# - host_include
# Hosts filter. `/DC Pattern/Cluster Patter/Host Pattern`.
# Pattern matches name, pattern syntax: simple patterns https://docs.netdata.cloud/libnetdata/simple_pattern/
# Syntax:
# host_include:
# - '/DC1/*' # all datacenter DC1 hosts
# - '/DC2/*/!Host2 *' # all datacenter DC2 hosts except HOST2
# - '/DC3/Cluster3/*' # all datacenter DC3 cluster Cluster3 hosts
#
# - vm_include
# VMs filter. `/DC Pattern/Cluster Patter/Host Pattern/VM Pattern`.
# Pattern matches name, pattern syntax: simple patterns https://docs.netdata.cloud/libnetdata/simple_pattern/
# Syntax:
# vm_include:
# - '/DC1/*' # all datacenter DC1 vms
# - '/DC2/*/*/!VM2 *' # all datacenter DC2 vms except VM2
# - '/DC3/Cluster3/*' # all datacenter DC3 cluster Cluster3 vms
#
# - host_metrics
# Add additional hierarchy data to the host chart id.
# Template: "host-ID_name-HOSTNAME_cluster-CLUSTERNAME_datacenter-DATACENTERNAME"
# Syntax:
# host_metrics:
# name: yes/no # add host name
# cluster: yes/no # add cluster name
# datacenter: yes/no # add datacenter name
#
# - vm_metrics
# Add additional hierarchy data to the vm chart id.
# Template: "vm-ID_name-VMNAME_host-HOSTNAME_cluster-CLUSTERNAME_datacenter-DATACENTERNAME"
# Syntax:
# vm_metrics:
# name: yes/no # add vm name
# host: yes/no # add host name
# cluster: yes/no # add cluster name
# datacenter: yes/no # add datacenter name
#
# - tls_skip_verify
# Whether to skip verifying server's certificate chain and hostname.
# Syntax:
# tls_skip_verify: yes/no
#
# - tls_ca
# Certificate authority that client use when verifying server certificates.
# Syntax:
# tls_ca: path/to/ca.pem
#
# - tls_cert
# Client tls certificate.
# Syntax:
# tls_cert: path/to/cert.pem
#
# - tls_key
# Client tls key.
# Syntax:
# tls_key: path/to/key.pem
#
#
# [ JOB defaults ]:
# timeout : 20
# tls_skip_verify : no
# discovery_interval : 300
# host_include : ['/*']
# vm_include : ['/*']
# host_metrics : {name: yes, cluster: yes, datacenter: yes}
# vm_metrics : {name: yes, host: yes, cluster: yes, datacenter: yes}
#
#
# [ JOB mandatory parameters ]:
# - name
# - url
# - username
# - password
#
# ------------------------------------------------MODULE-CONFIGURATION--------------------------------------------------
# [ GLOBAL ]
# update_every : 20
# do not decrease the value, vmware real-time stats generated at the 20-seconds specificity.
# autodetection_retry : 0
# priority : 70000
#
# [ JOBS ]
jobs:
- name: vcenterMain
url: https://*********** (private IP same as accessed through browser for vsphere)
username: support@vsphere.local
password: ***********
host_include: ['/*']
vm_include: ['/*']
tls_skip_verify: yes
# - name : vcenter2
# url : https://203.0.113.10
# username : admin@vsphere.local
# password : somepasswordI am using support@vsphere.local as that is the account I use myself not sure if it has to be admin, trying to test net-data before showing my manager since I would like to do some setup before involving him. Thank you for your help! |
Beta Was this translation helpful? Give feedback.
-
|
@Trash7276 you need to align the values jobs:
- name: vcenterMain
url: https://*********** (private IP same as accessed through browser for vsphere)
username: support@vsphere.local
password: ***********
host_include: ['/*']
vm_include: ['/*']
tls_skip_verify: yes |
Beta Was this translation helpful? Give feedback.
-
|
@ilyam8 Sorry to be a pain, are you able to elaborate more as the example used on the website https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/vsphere is : jobs:
and mine is : jobs:
I am not sure how mine needs to be aligned |
Beta Was this translation helpful? Give feedback.
-
|
The one you posted above has not aligned keys, it is not valid YAML syntax
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks I have managed to edit it correctly, can see from the logs below its now logging and making charts for the hosts and vms however on the cloud overview nothing is showing for vpshere vsphere debug outputnetdata@kasm-virtual-machine:/usr/libexec/netdata/plugins.d$ ./go.d.plugin -d -m vsphere [ DEBUG ] main[main] main.go:111 plugin: name=go.d, version=v0.32.2 [ DEBUG ] main[main] main.go:113 current user: name=netdata, uid=127 [ INFO ] main[main] agent.go:106 instance is started [ INFO ] main[main] setup.go:40 loading config file [ INFO ] main[main] setup.go:48 looking for 'go.d.conf' in [/etc/netdata /usr/lib/netdata/conf.d] [ INFO ] main[main] setup.go:55 found '/usr/lib/netdata/conf.d/go.d.conf [ INFO ] main[main] setup.go:62 config successfully loaded [ INFO ] main[main] agent.go:110 using config: enabled 'true', default_run 'true', max_procs '0' [ INFO ] main[main] setup.go:67 loading modules [ INFO ] main[main] setup.go:86 enabled/registered modules: 1/64 [ INFO ] main[main] setup.go:91 building discovery config [ INFO ] main[main] setup.go:121 looking for 'vsphere.conf' in [/etc/netdata/go.d /usr/lib/netdata/conf.d/go.d] [ INFO ] main[main] setup.go:137 found '/etc/netdata/go.d/vsphere.conf [ INFO ] main[main] setup.go:142 dummy/read/watch paths: 0/1/0 [ INFO ] discovery[manager] manager.go:90 registered discoverers: [file discovery: [file reader]] [ INFO ] discovery[manager] manager.go:95 instance is started [ INFO ] run[manager] run.go:30 instance is started [ INFO ] build[manager] build.go:106 instance is started [ INFO ] discovery[file manager] discovery.go:71 instance is started [ INFO ] discovery[file reader] read.go:39 instance is started [ INFO ] discovery[file reader] read.go:40 instance is stopped [ DEBUG ] build[manager] build.go:153 received config group ('/etc/netdata/go.d/vsphere.conf'): 1 jobs (added: 1, removed: 0) [ DEBUG ] build[manager] build.go:302 building vsphere[vcenter1] job, config: map[provider:file reader source:/etc/netdata/go.d/vsphere.conf autodetection_retry:0 host_include:[/] module:vsphere name:vcenter1 password:******** priority:70000 tls_skip_verify:true update_every:20 url:https://********* username:************ vm_include:[/*]] [ DEBUG ] run[manager] run.go:41 tick 0 [ DEBUG ] vsphere[vcenter1] discover.go:94 discovering : starting resource discovering process [ DEBUG ] vsphere[vcenter1] discover.go:102 discovering : found 1 dcs, process took 3.117145ms [ DEBUG ] vsphere[vcenter1] discover.go:109 discovering : found 5 folders, process took 3.176403ms [ DEBUG ] vsphere[vcenter1] discover.go:116 discovering : found 3 clusters, process took 2.455002ms [ DEBUG ] vsphere[vcenter1] discover.go:123 discovering : found 3 hosts, process took 9.458899ms [ DEBUG ] vsphere[vcenter1] discover.go:130 discovering : found 3 vms, process took 10.098115ms [ INFO ] vsphere[vcenter1] discover.go:140 discovering : found 1 dcs, 5 folders, 3 clusters (3 dummy), 3 hosts, 44 vms, process took 28.473468ms [ DEBUG ] vsphere[vcenter1] build.go:12 discovering : building : starting building resources process [ INFO ] vsphere[vcenter1] build.go:164 discovering : building : removed 23 vms (not powered on) [ INFO ] vsphere[vcenter1] build.go:23 discovering : building : built 1/1 dcs, 5/5 folders, 3/3 clusters, 3/3 hosts, 21/44 vms, process took 52.545µs [ DEBUG ] vsphere[vcenter1] hierarchy.go:10 discovering : hierarchy : start setting resources hierarchy process [ INFO ] vsphere[vcenter1] hierarchy.go:18 discovering : hierarchy : set 3/3 clusters, 3/3 hosts, 21/21 vms, process took 25.685µs [ DEBUG ] vsphere[vcenter1] filter.go:24 discovering : filtering : starting filtering resources process [ DEBUG ] vsphere[vcenter1] filter.go:45 discovering : filtering : removed 0 unmatched hosts [ DEBUG ] vsphere[vcenter1] filter.go:56 discovering : filtering : removed 0 unmatched vms [ INFO ] vsphere[vcenter1] filter.go:29 discovering : filtering : filtered 0/3 hosts, 0/21 vms, process took 46.435µs [ DEBUG ] vsphere[vcenter1] metric_lists.go:14 discovering : metric lists : starting resources metric lists collection process [ INFO ] vsphere[vcenter1] metric_lists.go:30 discovering : metric lists : collected metric lists for 3/3 hosts, 21/21 vms, process took 57.834774ms [ INFO ] vsphere[vcenter1] discover.go:74 discovering : discovered 3/3 hosts, 21/44 vms, the whole process took 98.829554ms [ INFO ] vsphere[vcenter1] discover.go:7 starting discovery process, will do discovery every 5m0s [ INFO ] vsphere[vcenter1] job.go:171 check success [ INFO ] vsphere[vcenter1] job.go:191 started, data collection interval 20s I can see the individual virtual machines also being picked up and charts being created but still nothing on the dashboard on app.netdata.cloud
|
Beta Was this translation helpful? Give feedback.
-
If you
Do you see vsphere charts there? |
Beta Was this translation helpful? Give feedback.
-
|
Yes once back into the local dashboard it populates, had to remove the node and add it again to get the data to show. Working now thank you |
Beta Was this translation helpful? Give feedback.
@Trash7276 you need to align the values