Closed nlamirault closed 2 years ago
Looks like if you are using customConfig
, you have to manually define host metrics source and prometheus sink:
customConfig:
sources:
host-metrics:
type: host_metrics
scrape_interval_secs: 10
filesystem:
devices:
excludes: ["binfmt_misc"]
sinks:
prom-exporter:
type: prometheus_exporter
inputs:
- host-metrics
address: 0.0.0.0:9598
Too bad it's missing in the documentation and you need to dig through helm helpers code.
What @juris mentioned is correct. If you are providing your own custom config, you have to wire up the prom exporter yourself. I'll leave this open to improve the documentation.
Thanks, it works fine.
@jszwedko Hello. Please tell me. Is there documentation on how to set up vector monitoring if I use helm chart + customconfig?
@juris This is wrong. You should use.
sources:
vector_metrics:
type: internal_metrics
scrape_interval_secs: 10
sinks:
prom-exporter:
type: prometheus_exporter
inputs:
- vector_metrics
address: 0.0.0.0:9598
podMonitor:
# podMonitor.enabled -- If true, create a PodMonitor for Vector.
enabled: true
Hi, I configure the chart like that :
PodMonitor is generated like that :
but the daemonset does not have the metrics port :
Any idea how can i configure the Helm chart to add the Prometheus metrics port ? Thanks.