News for hackers. Stuff that matters.
Re:Real World Examples of GPT-3 Plain Language Root Cause Su... by draugadrotten on Thursday March 25, 2021 @05:55PM (#26585967)
The human-readable text is very nice. However, these are not Root Causes:

* The root cause of the issue was that the Jenkins master was not able to connect to the vCenter server. ==> Why was it not?

* The root cause was a drive failed error ==> Why did the drive fail?

* The root cause was that the Slack API was rate limited. => Why was it rate limited?

These exampled from the article may be human-readable errors, but that doesn't make them root causes.

To have a root cause analysis, try asking Why five times. https://en.wikipedia.org/wiki/Five_whys

Re:Real World Examples of GPT-3 Plain Language Root Cause Su... by Ajs1 on Thursday March 25, 2021 @06:25PM (#26586373)
good point. This is the unfiltered response from the GPT-3 prompt, and the phrase "root cause" is a bit of an overstatement by GPT-3. However the collection of log events that are in the actual reports are far more descriptive. You can find examples here: https://www.zebrium.com/blog/using-gpt-3-with-zebrium-for-pl... and here: https://www.zebrium.com/blog/is-autonomous-monitoring-the-an...
Re:Real World Examples of GPT-3 Plain Language Root Cause Su... by mlthoughts2018 on Thursday March 25, 2021 @08:24PM (#26587452)
“Root cause” is relative. To the CEO the root cause is “some engineering thing broke.” To the data engineer the root cause may be that a human config error led to a rogue process that caused a VM disk to fill up. To a quantum super-intelligence the root cause may be that in Everett Branch 2765425 atom 67896533 collided with atom 78532578.

(Just kidding. The space of Everett branches is not countable.)