This would allow repeated issues to be well documented.
On iOS Firefox, when clicking “pricing” on the menu, it scrolls to the proper location, but does not close the menu. Closing the menu causes it to jump to the top of the page. Super annoying.
And thanks for the bug report, I'll take a look
That said, a tool that runs through existing runbooks and improves them or suggests new ones would be extremely useful IMHO.
Keep in mind, they are suggestions. It sounds like the product will automatically execute runbooks but hold suggestions for engineer input. This would move it from “suggestion” to “automatically do X”
Also, sometimes LLMs are wrong.
Yea, this is a big challenge for us. We're using a variety of strategies to make sure hallucinations are rare, but that's why we're also committed to not executing actions that modify your cluster unless explicitly specified in a runbook
Enterprises implement stringent Change Management procedures.
If you are making any change to a Prod environment it needs to be thoroughly documented.
Because when it goes wrong you will want to know what it did. When you discover something new, you are going to want to be able to change the runbook. New employees are going to want to learn how things work from the runbook.
Why WOULDN'T you want to document what it is doing? I would never trust an AI that didn't tell me what it was doing and why.