![]() ![]() Pro: Annotations are persistent, so they don't need to be recreated if a pod is removed. We recommend editing the pod template over editing the service definition, as this requires fewer permissions (for example, if you don't have access to services). This is the most reliable way to ensure persistency of annotations. If you have full control over the pod template or service definition, we recommend adding the annotations by editing these files. See below to decide which approach fits your scenario best. There are multiple ways to place annotations on pods or services. th: 'builtin:default' Annotation best practices For these exporter pods, add the following annotation: Some exporter pods such as node-exporter, kube-state-metrics, and openshift-state-metrics require RBAC authorization. tls.key='secret:kubernetes-config:etcd-metric-client:tls.key' Role-based access control (RBAC) authorization for metric ingestion tls.crt='secret:kubernetes-config:etcd-metric-client:tls.crt' Plaintext copy download /tls.ca.crt='configmap:kubernetes-config:etcd-metric-serving-ca:ca-bundle.crt' *bytes filters all metrics ending with bytes.redis_db* filters all metrics starting with redis_db.This symbol allows you to filter metrics keys that begin with, end with, or contain a particular sequence, such as: The filter syntax also supports the asterisk ( *). If no filter annotation is defined, all metrics are collected. Use /filter to define a filter that allows you to include ( "mode": "include") or exclude (( "mode": "exclude")) a list of metrics. The default value is false, because most exporters expose their metrics via HTTP. Set /secure to true if you want to collect metrics that are exposed by an exporter via HTTPS. Use /path to override the default ( /metrics) Prometheus endpoint. Metrics port requiredīy default, Prometheus metrics are available at the first exposed TCP port of the pod. Set /scrape to 'true' to enable Dynatrace to collect Prometheus metrics exposed for this pod. Monitor Kubernetes namespaces, services, workloads, and podsĭynatrace collects metrics from any pods that are annotated with a /scrape property set to true in the pod definition.ĭepending on the actual exporter in a pod, you might need to set additional annotations to the pod definition in order to allow Dynatrace to properly ingest those metrics.In Dynatrace, go to your Kubernetes cluster settings page and enable An ActiveGate running inside the cluster will also provide improved performance. If your ActiveGate is running outside the monitored cluster (for example, in a VM or in a different Kubernetes cluster), it won't be able to scrape the Prometheus endpoint on pods that require authentication (such as RBAC or client authentication). We recommend that you use an ActiveGate that is running inside the Kubernetes cluster from which you want to scrape Prometheus metrics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |