You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for a bit of guidance here. We currently have a lot of clients we gather and send data to Google Ads using the PHP SDK. We do things like querying all of their ads and campaigns, as well as performance data to generate reports, as well as sending conversions back to Google.
Our google ads client is instantiated with its own logger that should be logging just to the Laravel log using withLogger, but also I don't believe our servers have grpc installed so I am imagining the service is falling back to using the REST API.
My issue is that our servers regularly fill up on disk space, due to the /tmp folder being filled up with tons of files full of response data from the Google ads API such as
The text was updated successfully, but these errors were encountered:
I think this is blocked by the logging feature of REST.
We were planning to provide support for it around the end of last year, but I was swamped with other priorities.
I'll find time to make this happen in this quarter.
Looking for a bit of guidance here. We currently have a lot of clients we gather and send data to Google Ads using the PHP SDK. We do things like querying all of their ads and campaigns, as well as performance data to generate reports, as well as sending conversions back to Google.
Our google ads client is instantiated with its own logger that should be logging just to the Laravel log using withLogger, but also I don't believe our servers have grpc installed so I am imagining the service is falling back to using the REST API.
My issue is that our servers regularly fill up on disk space, due to the /tmp folder being filled up with tons of files full of response data from the Google ads API such as
The text was updated successfully, but these errors were encountered: