@kapa.ai, for the Google Ads connector, is there a log level/configuration that allows us to see the request payload and API response when the connector makes calls to the Google Ads API? This would be really helpful for debugging API-related issues.

The knowledge sources do not explicitly document a built-in, production-ready log level setting for the Google Ads connector that exposes full request payloads and API responses. However, here is what the available information does tell us: Logging HTTP Calls in the Google Ads Connector What's currently available • The Python CDK has infrastructure to support debug-level logging by setting the environment variable

DEBUG=true

. This was mentioned in the context of a feature request for logging HTTP calls, and it may surface additional detail — but it is not guaranteed to include full request payloads or API responses for the Google Ads connector specifically. [GitHub Issue] • The Google Ads connector uses the

google-ads

Python library, which communicates via gRPC (not plain HTTP REST) for most streams. This means standard HTTP-level logging tools may not capture the actual request/response bodies. [google_ads.py] • Some streams (e.g.,

accessible_accounts

) do use REST/HTTP via the CDK's

HttpRequester

, where HTTP-level logging would be more applicable. [manifest.yaml] Workarounds mentioned by the community • Set

DEBUG=true

as an environment variable when running the connector — this enables debug-level logging in the CDK. • Use an nginx proxy with logging and route connector traffic through it. This was suggested as a temporary solution for debugging parent stream behavior. [GitHub Issue] What's not yet available There is no documented, out-of-the-box configuration option in the Google Ads connector to selectively log request payloads, query parameters, cursor values, or API responses at a granular level. A feature request for this exists but was closed as stale. [GitHub Issue] Summary: Your best current option is to try setting

DEBUG=true

when running the connector. For deeper inspection (especially of gRPC calls), a proxy-based approach is the most reliable workaround. A proper log-level feature for connectors has been discussed but not yet implemented. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.