Interviews for developers should say: This is an error on production. You have 10 min to find the solution on google.
This is more efficient than making developers write algorithms.

I've worked for an employer that conducted such an assignment but was not executed that well.
Depending on how specific the error I will come up with a long list of possibilities and the one you are looking for might not be in it as I don't know/can't analyze the environment.
A very specific log line like "nginx: <confixsyntax error here>" will give one solution but doesn't test the capabilities.

Good assignments are hard to create. Just take that into account. It is very possible to do this; including follow up questions to see if they understand the problem/solution.

Thanks for the information.

I like the idea

But if I'm being crass it would require too knowledge of the tech stack and access to git.

Could be a good entry point though to see if they ask good questions like "What view template engine are you using - could it be an unfiltered string from a CMS breaking the view?" Etc

I was interviewing a candidate once and we had a production outage. I recommended we hire them when they found the solution to the outage.

@Nanos you have a keen eye!

@Nanos generally speaking, that’s a pretty good sign 🪧

@Nanos if I built my own car, I’m pretty sure I’d never get another date. 🤣