You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we currently have limited support for Prometheus through our serviceMonitor.* and prometheusRule.* values, we can make the situation much better.
This option is recommended by the creators of statsd_exporter (need to check why, but its probably so that Prometheus associates the metrics to the actual Pod that is generating them)
I am not sure if all Pods will need the sidecar or just the scheduler
We would then configure AIRFLOW__METRICS__STATSD_HOST to be localhost
We would annotate the Pods with the sidecar to have prometheus.io/scrape: "true" and prometheus.io/port: "xxxx"
OPTION 2: as a central deployment
This would reduce the number of containers
We would then configure AIRFLOW__METRICS__STATSD_HOST to be the service of this deployment (but this is possibly a security risk, as other pods could send bad data if no NetworkPolicy prevents invalid access)
We would annotate the Deployment Pods to have prometheus.io/scrape: "true" and prometheus.io/port: "xxxx"
The existing serviceMonitor.* and prometheusRule.* values could be automatically configured (but there is an argument that these are configs for the user's Prometheus, and should not be managed by the chart).
For some reason, these resources are currently stored under the template/webserver/ folder (when they are not really specific to the webserver)
While we currently have limited support for Prometheus through our
serviceMonitor.*
andprometheusRule.*
values, we can make the situation much better.Tasks:
statsd_exporter
(need to check why, but its probably so that Prometheus associates the metrics to the actual Pod that is generating them)AIRFLOW__METRICS__STATSD_HOST
to be localhostprometheus.io/scrape: "true
" andprometheus.io/port: "xxxx"
AIRFLOW__METRICS__STATSD_HOST
to be the service of this deployment (but this is possibly a security risk, as other pods could send bad data if no NetworkPolicy prevents invalid access)prometheus.io/scrape: "true
" andprometheus.io/port: "xxxx"
prometheus.io/scrape: "true
" andprometheus.io/port: "xxxx"
serviceMonitor.*
andprometheusRule.*
values could be automatically configured (but there is an argument that these are configs for the user's Prometheus, and should not be managed by the chart).template/webserver/
folder (when they are not really specific to the webserver)Completing these tasks should replace the need for the following issues:
serviceMonitor
&prometheusRule
) #274The text was updated successfully, but these errors were encountered: