Versions Compared

Old Version 34

changes.mady.by.user Abhishek Chaturvedi

Saved on

compared with

New Version 35

changes.mady.by.user Abhishek Chaturvedi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agent install Setup Scenario

Steps

Kloudfuse stack & target both in same VPC and in same K8S cluster (Default)

This is the default scenario. Just use the provided values file for the agent and install.

Kloudfuse stack & target both in same VPC, but in different K8S cluster

Search for “url” _url in the provided file. Comment Wherever found, comment the Default Scenario and uncomment Scenario 1. For the IP address values needed, please see the following steps.

  • Get ingress internal IP

    Code Block
    kubectl get svc -n kfuse | grep kfuse-ingress-nginx-controller-internal
kfuse-ingress-nginx-controller-internal   LoadBalancer   10.53.250.80    10.53.232.3   80:32716/TCP,443:30767/TCP   125m

  • replace all settings with “_url” url suffix, for example:

    Code Block
    dd_url: http://10.53.250.80/ingester
logs_dd_url: "10.53.250.80:80"

Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)

Search for “url” _url in the provided file. Comment Wherever found, comment the Default Scenario and uncomment Scenario 2. update each of the “_url” settings with the Replace the customer.klodufuse.io with your custom DNS name entry.

  • replace all settings with “_url” url suffix, for example:

    Code Block
    dd_url: http://customer.kloudfuse.io/ingester
logs_dd_url: "customer.kloudfuse.io:443"

...

Code Block
ingester:
  config:
    hostTagIncludes:
    - kfuse
    - kube_cluster_name
    - kubernetes.io/hostname
    - node.kubernetes.io/instance-type
    - org_id
    - project
    - topology.kubernetes.io/region
    - topology.kubernetes.io/zone
    ...
    - custom_tag_name

Metadata for metrics collected using the openmetrics check

If using the above configuration, then the openmetrics check is enabled in the agent. See here for more details on what openmetrics check does. Kloudfuse agent (installed using the provided values file) employs a custom check (kf_openmetrics) to collect metadata (the “Description” and “Type” of metrics) for metrics collected using the openmetrics check, which. by default, doesn’t collect any metatada. To enable collection of metadata for these metrics, the sources are required to be annotated which will enable the agent auto-discovery for these pods and execute the custom check.

Kubernetes environment

To enable metrics metadata to be collected from a Kubernetes deployment or sts, follow these steps:

Code Block
  annotations:
    ad.datadoghq.com/orders.check_names: '["kf_openmetrics"]'
    ad.datadoghq.com/orders.init_configs: '[{}]'
    ad.datadoghq.com/orders.instances: '[ { "openmetrics_endpoint": "<http://%%host%%:%%port%%/metrics>"}
      ]'

Advance monitoring: Enable kubernetes_state_metrics

...