Using Existing Datadog Agent Install on Kubernetes

If you have an existing datadog agent, then you can use the same agent to send your data streams to the Kloudfuse platform.

Streaming to Kloudfuse in addition to Datadog

Datadog Agent supports dual shipping. To send the data to Kloudfuse in addition to the Datadog, add the following in the datadog agent helm values.

(Note the change for each stream as needed).

Under the agents.customAgentConfig key:

additional_endpoints:
  "http://<kfuse-ingress-external-ip>/ingester":
   - <api_key>
use_v2_api:
  series: true
logs_config:
  ...
  use_v2_api: false
  additional_endpoints:
    - api_key: <api_key>
      Host: <kfuse-ingress-external-ip>
      Port: 443
      use_compression: true
apm_config:
  ...
  additional_endpoints:
    "https://kfuse-ingress-external-ip>/ingester":
       - <api_key>
process_config:
  ...
  additional_endpoints:
    "https://kfuse-ingress-external-ip>":
       - <api_key>
orchestrator_explorer:
  ...
  orchestrator_additional_endpoints:
    "https://kfuse-ingress-external-ip>/ingester":
      - <api_key>
  manifest_collection:
    enabled: false 
metadata_providers:
  - name: host
    interval: 300

Under the clusterAgent.datadog_cluster_yaml key:

additional_endpoints:
  "http://<kfuse-ingress-external-ip>/ingester":
   - <api_key>
use_v2_api:
  series: true
process_config:
  ...
  additional_endpoints:
    "https://kfuse-ingress-external-ip>":
       - <api_key>
orchestrator_explorer:
  ...
  additional_endpoints:
    "https://kfuse-ingress-external-ip>":
       - <api_key>

External

Using Existing Datadog Agent Install on Kubernetes

Streaming to Kloudfuse in addition to Datadog

Related pages