help request: Datadog plugin config - can't define DogStatsD target with CRDs

[swo-ralf]

help request: Datadog plugin config - can't define DogStatsD target with CRDs

[shreemaan-abhishek]

@Revolyssup

[Revolyssup]

@swo-ralf Do you have any logs from ingress controller?

[Revolyssup]

@swo-ralf Can you check admin api to see if plugin metadata was created?
curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1'

[swo-ralf]

I did a kubectl port-forward to the apisix-admin K8s service and looks like it was not created:

$ curl http://127.0.0.1:9080/apisix/admin/plugin_metadata/datadog -H 'X-API-KEY: thekey'
{"message":"Key not found"}

$ curl http://127.0.0.1:9080/apisix/admin/plugin_metadata -H 'X-API-KEY: thekey'
{"total":0,"list":[]}

[Revolyssup]

@swo-ralf What about any logs from ingress controller??

[Revolyssup]

plugin-metadata-config-map

Will you also try removing the namespace: ingress-apisix from configmap

[swo-ralf]

@Revolyssup tried it without namespace and see the following error in log:

2024-01-05T10:40:12+08:00 �[31merror�[0m apisix/pluginconfig.go:139 failed to create pluginConfig: unexpected status code 400; error message: {"error_msg":"invalid configuration: additional properties forbidden, found name"}

Which I do not understand, because https://github.com/apache/apisix-ingress-controller/blob/7a9a0fab478861ed3a90f0793a65100ace9de047/conf/plugin-metadata-config-map.yaml shows exactly the same thing.

[Revolyssup]

@swo-ralf This has been fixed in apisix 3.7.0. Use apisix version 3.7.0>= please

[Revolyssup]

This was fixed here apache/apisix#10315

[swo-ralf]

I updated today to Apisix chart 1.10.0 and have Apisix 3.8.0 running and still see no change.
The last reported error with invalid config is fixed, but still host doesn't get changed away from localhost.

2024/01/22 09:38:15 [error] 49#49: *13349 [lua] datadog.lua:143: send_metric_over_udp(): failed to report request latency to dogstatsd server: host[127.0.0.1] port[8125] err: connection refused, context: ngx.timer, client: 10.224.0.4, server: 0.0.0.0:9080

Doesn't make a difference if I provide the plugin-metadata-config-map in the apisix namespace or omitting the namespace completely.

@Revolyssup What kind of information would be additional helpful to pinpoint the issue?

Thanks!