Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

For what it's worth, I'm fairly certain you can also just pipe the logs to /dev/null/ https://unix.stackexchange.com/questions/332019/replace-file-with-hard-link-to-dev-null On Wednesday, April 19, 2017 at 5:14:57 AM UTC+9, George (Cloud Platform Support) wrote: > > Hello Julian, > > You are en

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

Hello Julian, You are encouraged to create an issue tracker entry at http://issuetracker.google.com/, as this issue deserves the direct attention of the developers. Posting there may speed up the research for an eventual resolution. It is worthwhile providing a good use case, to facilitate in

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

Isn't the qualifier for the beta logging read command --verbosity (not --severity)? gcloud beta logging read --limit=1 --verbosity=none However, when this is used it still produces a log in the ~/.config directory that contains all log level entries, including "INFO" level. Perhaps I have misund

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

As a first approach, you may try using the --severity=SEVERITY flag, or filter the read entries by using --limit=LIMIT, all this to diminish from start the general volume of logs. You may also consider implementing a cron job in Linux, to avoid having to delete unwanted files manually. -- Y

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

Thanks for the info. We have no use for the gcloud beta logging tool's log files, and would like to disable them. Right now we are simply deleting them after the command terminates, but we would like to avoid such a heavyweight approach, not to mention the considerable I/O load they cause to our s

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

This is intended behavior: "The gcloud tool creates and stores logs in a log file that you can query, located at $HOME/.config/gcloud/logs. ", as documented at "Tips, Troubleshooting, & Known Issues ". Do you use the logs in the ~/.config/

Re: [google-appengine] Re: gcloud beta logging read creates huge log files in .config

Hello, The size of the files in the ~/.config subdir appear to scale with the number of logs downloaded by the gcloud tool. We are downloading a day's worth of logs at a time, for a busy application which produces around 750k log entries per day. (Downloading this many log entries takes at least

[google-appengine] Re: gcloud beta logging read creates huge log files in .config

Hello Julian, We could not reproduce the issue locally. The files in our linux machine’s ~/.config/gcloud/logs directory are reasonably small. You may attempt to reduce the size of your file by applying filtering more aggressively. Details on filter setup are to be found on the “Command Line