08 Jul 2021 04:22 PM - last edited on 26 Nov 2021 08:26 AM by Karolina_Linda
I'm trying to understand how Dynatrace One Agent is expected to be configured in a Kubernetes environment. In my case Azure (AKS).
I see One Agent deployed to each node using a Kubernetes Daemonset. Is each deployed application POD on the node expected to share and communicate with the One Agent instance deployed locally on each node or will each application POD require its own One Agent?
I'm struggling to figure out how the http://localhost:14499/metrics/ingest endpoint is expected to work for application PODs.
Solved! Go to Solution.
04 Jan 2022 02:30 PM
Hi Community, does anyone have some tips to overcome struggles mentioned above?
25 May 2022 12:39 PM
I'm also struggling with this, has anybody made any advancements on this topic?
30 Jun 2022 04:37 AM
Same here, I'd like to know how can I configure my PODs to call OneAgent internal apis 😞
30 Jun 2022 11:24 AM
The way to create a Metrics v2 endpoint inside of a Kubernetes cluster is to deploy a containerized ActiveGate using the Dynakube. You can read about this here. Notice the capabilities parameter for the ActiveGate includes a `metrics-ingest` value.
04 Oct 2022 02:04 PM
@mreider i'm attempting to do the same within an EKS k8s cluster. i have a containerize activegate via Dynakube CRD with metrics-ingest capability specified. the problem is finding the documentation how to proceed from here. i can hit the k8s service endpoint for activegate via curl from another namespace/pod but get this error:
Error: 405 HTTP method POST is not supported by this URL<br/>Uri: /metrics/ingest
04 Oct 2022 03:15 PM
given the activegate k8s service/endpoint definition, i'm trying to curl a test custom metric to:
https://<activegate_svcname>.dynatrace/metrics/ingest
the host and port receive the request but response is the 405 HTTP error mentioned above.
04 Oct 2022 04:25 PM
trying a different url:
https://<activegate_svcname>.dynatrace/api/v2/metrics/ingest
the host receives the request but response is 404 failed to resolve tenant
30 Jun 2022 03:21 PM
@mreider, Hi! Thank you for the response, I tried to edit our Dynakube to add `metrics-ingest`, but this error occurs:
The DynaKube's specification tries to use an invalid capability in ActiveGate section, invalid capability=metrics-ingest.
Make sure you correctly specify the ActiveGate capabilities in your custom resource.
So, dynakube cr doesnt allow to edit ? I Must run the kubectl apply again ?
30 Jun 2022 03:28 PM
And what version of the Dynatrace Operator are you using? (must be > v0.4.0)
30 Jun 2022 03:33 PM
@mreider where can I see what Dynatrace Operator version I'm using ? The docker image for operator deployment is: image: docker.io/dynatrace/dynatrace-oneagent-operator:v0.10.2
30 Jun 2022 03:36 PM
@mreider I already found: Im using 0.3.0, so need to update my Dynatrace Operator 😉 Thank you!
17 Aug 2022 02:54 PM
I did install dynatrace operator
https://github.com/Dynatrace/dynatrace-operator/releases/download/v0.7.2/kubernetes.yaml
This has installed the active gate stateful set , however when i try to navigate for /metric end point , the active gate seems not expoed.
I did add additional param of metrics-ingest in yaml file