usually, ETCD offers metrics in Prometheus format - you can leverage our feature to scrape Prometheus endpoints in k8s to get these metrics to Dynatrace. In K8s I would recommend this approach over the extension based approach mentioned by @bradley_danyo
Has anyone actually implemented ingestion of etcd Prometheus metrics? I'm running Dynatrace Operator 0.11.2 (full stack). I added the following in etcd pods but no etcd metrics are ingested. I have Prometheus metrics being ingested from several other pods from the same k8s cluster (NOT Openshift)
metrics.dynatrace.com/http.auth: builtin:default metrics.dynatrace.com/port: "2379" metrics.dynatrace.com/scrape: "true" metrics.dynatrace.com/secure: "true" metrics.dynatrace.com/tls.ca.crt: secretdynatrace-dev-tls-etcd-own:ca.crt metrics.dynatrace.com/tls.crt: secretdynatrace-dev-tls-etcd-own:tls.crt metrics.dynatrace.com/tls.key: secretdynatrace-dev-tls-etcd-own:tls.key
Appreciate any help/insights
Did you check the response code the operator returned? Use the dsfm metric
dsfm:active_gate.kubernetes.api.query_count and filter for desired endpoint.