[fellerts]

Just want to chip in and say that I wholeheartedly agree with you. I'm not a cloud developer either, but I'm regularly forced into what's apparently called "Google Cloud's operations suite" to grovel through logs. Compared to working with Linux journals using the tried and true text manipulation tools, it feels like looking through a straw with oven mitts on. I'd happily download a 500 MB text file instead, but there is an arbitrary limit to how much I can grab (10k lines IIRC). Maybe we're just out of touch.

[remus]

> but I'm regularly forced into what's apparently called "Google Cloud's operations suite" to grovel through logs

Is this google cloud logging? If so, personally I quite like it, especially for looking through logs from multiple sources at the same time. Being able to put all your logs through there, and then search them with a simple query language, feels very convenient.

[pas]

it's ridiculously slow. and compared to how expensive it is ... it's robbery in daylight.

[debarshri]

It fairly risky to download 500MB of log and analyse it locally in the machine. I know People do it anyways. Just saying.

[dstroot]

Risky how exactly? If it has data in it that it shouldn't it's a problem no matter where it resides.

[ta1243]

In theory a logfile could contain privileged information (indeed it almost certainly will - IP addresses etc), putting that on a laptop increases risk of losing it.

[debarshri]

It is not about what data is in the log. It is about the fact that once the data is download, it most likely going to stay in the machine.

Logs often contain privileged info, if not reveal a bit about how the application behaves. It is risky to do that.

[kiitos]

If logs contain privileged info, then the damage is done the moment they're published. Whether or not they're downloaded to a laptop is irrelevant, the risk impact is the same.