Tell HN: ChatGPT is fantastic for finding and solving issues in logs

Post by _xivi » Thu, Apr 20, 2023, 6:38 PM UTC

sharemywin wrote: post #65

zeroDivisible wrote: post #28

This is a great feature and I did use it few times to test. However, be aware of potentially leaking your company's private or sensitive information when doing this.

https://openai.com/policies/api-data-usage-policies OpenAI will not use data submitted by customers via our API to train or improve our models, unless you explicitly decide to share your data with us for this purpose. You can opt-in to share data. Any data sent through the API will be retained for abuse and misuse monitoring purposes for a maximum of 30 days, after which it will be deleted (unless otherwise required…

Post by s3p » Thu, Apr 20, 2023, 6:44 PM UTC

akiselev wrote: post #75

TacticalCoder wrote: post #26

How does that work with logs? Logs are often... Huge? How many lines of logs can you paste? Because if I first need to narrow down the log to the problematic part, I kinda already have my problem right there no? Or do you mean I do something like grab the lines with "error" in the log, hoping there aren't too many, then ask ChatGPT what it thinks about this: [ 0.135036] kernel: ACPI Error: AE_NOT_FOUND, During name l…

That log line ( with the four space at the front for HN formatting) is 40 tokens [1]. You can easily fit several hundred log lines with GPT4 8k context and with the incoming 32K context, you'll be able to fit close to a thousand log lines. That's a lot of context, especially if you can prefilter from relevant services, nodes, etc. or provide a multi-node trace [1] https://platform.openai.com/tokenizer

Post by skrebbel » Thu, Apr 20, 2023, 6:57 PM UTC

akiselev wrote: post #80

skrebbel wrote: post #79

Earlier quoted context omitted.

Yeah but… i can look through 100 log lines manually faster than writing a good gpt prompt. This would get useful if I can easily paste like 1M lines of logs (a few minutes of data for us), but even if that would work, it’d be prohibitively expensive I think. In other words, I still don’t completely grok the use case that’s being shared here.

The use case here is looking through logs for software that aren't familiar, especially stuff that gets touched too infrequently to internalize like, say, driver logs on a Linux workstation. If it's faster for you to read the logs yourself, you should continue to do that. If it's bespoke personal or commercial software, chances are GPT isn't going to be trained on its meaning anyway. Most people aren't going to be fa…

Post by dragonwriter » Thu, Apr 20, 2023, 7:00 PM UTC

chaorace wrote: post #104

simonw wrote: post #70

Earlier quoted context omitted.

I think there's a widely held misconception that anything you paste into GPT-4 will be used as raw training data by the model. Some people even seem to believe that it's learning continuously, so something you paste in could show up in an answer for another user a few minutes later. My mental model of how this works is somewhat different: - It takes months to train a model on raw data, and OpenAI train new ones (that…

I think it's more about being against the principle of piping potentially sensitive data to any third party. True, OpenAI doesn't have any real motivation to randomly pluck your data and decide to do something horrible to you with it... but they could . More importantly, circumstances can and will change as time goes on. If your logs change hands as part of a buyout or cyberattack, you'll have no recourse.

Post by personjerry » Thu, Apr 20, 2023, 7:07 PM UTC