The readme page of our proxy service on Github is the most accurate & updated source.

​
Doctor Droid Proxy Service: Just-In-Time Data Access

Doctor Droid’s proxy agent enables you to connect DrDroid with your k8s cluster and any other data source integrations within your VPC. For example, while investigating some issues, it might be required to run kubectl commands or data fetching query in mongoDB instance that might be within your VPC. Using the proxy agent enables the Doctor Droid platform to query commands / fetch data during an investigation. The Agent runs inside your VPC and acts as a reverse proxy to connect with your metric sources and send metrics and related data to doctor droid cloud platform. The agent is designed to be lightweight and easy to deploy with only egress tcp calls to Doctor Droid Cloud Platform. VPC Agent Currently, the agent supports the following metric sources in your VPC:
  • Grafana
  • Grafana Loki
  • Cloudwatch
  • Kubernetes
  • Azure AKS (via native Kubernetes)
  • AWS EKS (via native Kubernetes)
  • GKE (via native Kubernetes)
  • New Relic
  • Datadog
  • Opensearch
  • MongoDB
  • Github
  • Postgres
  • Any SQL Database (via Sql Connection String)
  • Bash Commands
Releasing soon (reach out to us if you need support for these or any other source):
  • Azure

​
Env vars

Env Var NameDescriptionRequired
DRD_CLOUD_API_TOKENAuthentication token for doctor droid platformTrue

​
Installation

To get started create an agent authentication token by visiting site

​
Docker Compose

  1. Create credentials/secret.yaml file with valid credentials. Secrets format for different connections can be referenced from: credentials/credentials_template.yaml.
Command: 
./deploy_docker.sh <API_TOKEN>
For any update the agent, re-run the command.

​
Helm

  1. Add the secrets for the integrations in helm/configmap.yaml file. Refer to the image below for a sample: Screenshot 2024-12-20 at 14 02 43
Command: 
cd helm
./deploy_helm.sh <API_TOKEN>
  • The agent will be installed in the namespace ‘drdroid’ by default. This can be changed in the helm/deploy_helm.sh file.
  • Agent updates the image automatically every day at 00:00 UTC.
  • Agent will have read access to the cluster and will be able to fetch the metrics from the cluster.
  • For teams deploying with Helm, the agent by default has access to the kubernetes cluster where it’s installed. This does not require any entry into configmap.yaml.
For any more questions or queries, reach out to our team or raise an issue on Github.