The configuration file above can be used to deploy Prometheus Server with job_name: 'antrea-agents' kubernetes_sd_configs: - role: pod scheme: https tls_config: ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt insecure_skip_verify: true bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token relabel_configs: - source_labels: action: keep regex: kube-system antrea-agent - source_labels: target_label: instance Reading metrics also requires access to the “/metrics” API Prometheus requires access to Kubernetes API resources for the service discoveryĬapability. Prometheus integration with Antrea is validated as part of CI using Prometheus v2.19.3. Prometheus Configuration Prometheus version Parameter to true in the Controller and the Agent configurations. Antrea ConfigurationĮnable Prometheus metrics listener by setting enablePrometheusMetrics So Prometheus can scrape the metrics of any additionalĬomponents which are added to the cluster without further configuration changes. One of Prometheus capabilities is self-discovery of Kubernetes services whichĮxpose their metrics. Prometheus can provide visibility by integrating with other products such as Prometheus is capable of collecting metrics from various KubernetesĬomponents, storing and providing alerts. Prometheus is an open source monitoring and alerting The configuration of Prometheus server to operate with the Antrea components. Prometheus server can monitor various metrics and provide an observation of theĪntrea Controller and Agent components. Using Fluentd to collect Network policy logs.
0 kommentar(er)
