sichenzhao
sichenzhao
> You can build and test your changes using our [CLI tool `ddev`](https://datadoghq.dev/integrations-core/setup/). After installing `ddev`, you can spin up a test environment for clickhouse using `ddev env start clickhouse...
Hi there, how do we build/test the change locally?
we have recently updated from 0.14.0 to 0.18.0, seeing similar behavior after updates: for us, it's throttling error ``` 2025-09-15T11:01:46.257976091Z {"level":"info","msg":"All records are already up to date","time":"2025-09-15T11:01:46Z"} 2025-09-15T12:02:06.328077978Z {"level":"error","msg":"Failed to...
this is taken care of and tested in 1.18.0. It's working. Thanks!
@jcarvalho could you please take a look?
or shall I ping @cyrilgdn ?
To explain, for people use [tailscale](https://tailscale.com) for example, we will have different VPN hostname for postgresSQL connection. That's a different url than url AWS can take for AWS API related...
kindly ping @cyrilgdn to see if my answer above makes sense. Thank you!
a kind ping on @cyrilgdn
@cyrilgdn could you please take a look? i think it should be ready for testing