Update team one readme with information on how logging works. (#259)

Update team one readme with information on how logging works.

Related to #228

python/teams/team-one/readme.md

@@ -153,6 +153,16 @@ Once on Waoonet's profile, the agents focused on counting the comments that had
 | Total          | 28%  (120/422) |
 
 
+### Logging in Team One Agents 
+
+Team One agents can emit several log events that can be consumed by a log handler (see the example log handler in [utils.py](src/team_one/utils.py)). A list of currently emitted events are:
+
+- OrchestrationEvent : emitted by a an [Orchestrator](src/team_one/agents/base_orchestrator.py) agent.
+- WebSurferEvent : emitted by a [WebSurfer](src/team_one/agents/multimodal_web_surfer/multimodal_web_surfer.py) agent.
+
+In addition, developers can also handle and process logs generated from the AGNext core library (e.g., LLMCallEvent etc). See  the example log handler in [utils.py](src/team_one/utils.py) on how this can be implemented. By default, the logs are written to a file named `log.jsonl` which can be configured as a parameter to the defined log handler. These logs can be parsed to retrieved data agent actions.
+
+
 # Setup
 
 
@@ -220,4 +230,4 @@ Some functionalities, such as using web-search requires an API key for Bing.
 You can set it using:
 ```bash
 export BING_API_KEY=xxxxxxx
-```
+```