This message was deleted.

you will still need to make it available on all the nodes. the extension has to be available inside the extensions directory.

it is inside the extension directory

then just adding to loadList is enough.

I have this

druid_extensions_loadList: '["druid-histogram","druid-datasketches","postgresql-metadata-storage","druid-kinesis-indexing-service","druid-parquet-extensions","druid-basic-security","druid-s3-extensions","druid-kafka-indexing-service","statsd-emitter","druid-avro-extensions","druid-lookups-cached-global"]',
                    druid_emitter_statsd_dogstatsdConstantTags: pulumi.interpolate`["cluster:${clusterName}"]`,
                    druid_emitter_statsd_hostname: 'localhost',
                    druid_emitter: 'statsd',
                    druid_emitter_logging_logLevel: 'debug',
                    druid_monitoring_emissionPeriod: 'PT15S',
                    druid_emitter_statsd_port: '8125',
                    druid_emitter_statsd_dogstatsd: 'true',
                    druid_emitter_statsd_includeHost: 'true',

This is depends on how DD agent is installed. Is this on Kubernetes? DD agent is typically installed on the host of Kubernetes itself, so you have to pass the Host ip address into your pod via environment variable. And then on boot, you read that environment variable and pass it to the config file.

Yes, DD is on kubernetes, each node has different pods running in it, Druid, DD agent, … Druid prod has different IP than DD agent pod, so hostname cant be

localhost

, it would need to be DD’s agent pod IP I guess. Do you mean it can be the node IP itself? some test I have been doing indicates that needs to be DD’s agent pod IP, if I do this from Druid pod/container it works:

echo -n "custom_metric_druid_dd_agent_pod_ip_prod:60|g|#shell" | nc -u -w0 10.5.128.196 8125

10.5.128.196

is the pod where DD agent is running