Tweak log levels

[enyst]

End-user friendly description of the problem this fixes or functionality that this introduces

• Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below
  Restore visible logs for each action and observation when ran locally.

---

Give a summary of what the PR does, explaining any non-trivial design decisions

This PR proposes a few tweaks for log levels:

• display at info the action and the obs (ref slack) when LOG_ALL_EVENTS env var is set
• send to debug channel most of logging in github.py since that is not active in most use cases and on local it sounds like something's wrong.

---

Link of any specific issues this addresses

---

To run this PR locally, use the following command:

docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:1aa983c-nikolaik   --name openhands-app-1aa983c   docker.all-hands.dev/all-hands-ai/openhands:1aa983c

[tofarr]

LGTM

[rbren]

I explicitly do not want actions and observations in the info logs--will follow up

[rbren]

@enyst we need to keep actions and observations out of the default info logs, because they can contain (a) a LOT of information, and (b) private information

I'd support having an env var that swaps them from debug into info though, like LOG_ALL_EVENTS

[enyst]

@enyst we need to keep actions and observations out of the default info logs, because they can contain (a) a LOT of information, and (b) private information

Okay. Oh, this is an issue on the hosted version, I suppose? On local it looks really strange to not tell the user anything.

Env var sounds good.

[rbren]

Yeah I'd say it's an issue in any kind of multi-tenant environment.

Also, ideally, the UI would give you all this information, and the server logs should really just be there to know "is the server functioning properly." I think right now it's kind of a hacky way to gain the level of agent observability we want in the UI but don't have.

[enyst]

On further thought, we already have other env vars changing the logging behavior, like LOG_TO_FILE and SKIP_CONTAINER_LOGS somewhere, adding another is not helping predictability. FWIW maybe I didn't lose track yet, but it's going to happen. 😅

Does this work though as a temporary measure? I think we need to think this over.

[rbren]

Unblocking but left one comment!