Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tmp folder is being filled up with files containing logs of of REST API calls. #802

Open
scottjohnson623 opened this issue Dec 27, 2024 · 0 comments

Comments

@scottjohnson623
Copy link

Hello,

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

{
      "campaign": {
        "resourceName": "xxxx",
        "advertisingChannelType": "DISPLAY",
        "id": "xxxx"
      },
      "metrics": {
        "clicks": "xxxx",
        "costMicros": "xxxx",
        "impressions": "xxxx"
      },
      "adGroupAd": {
        "resourceName": "xxxx",
        "ad": {
          "type": "RESPONSIVE_DISPLAY_AD",
          "resourceName": "xxxx",
          "id": "xxxx"
        }
      },
      "segments": {
        "date": "xxxx"
      }
    },

I have been digging around the library to try and figure out what is the cause of these files been written to the tmp folder so I can stop them from being written, but haven't had any luck with any configuration / setup with the sdk to stop them from logging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant