Best Practices for Filtering Trace Logs in Phoenix
Hi everyone! 馃憢 Hope you're all doing well. We've recently rolled out Phoenix in production and it's been an awesome experience so far! I'm now working on a project with Agno and using their team config. One challenge I鈥檝e run into is that the trace logs can get quite verbose鈥攅specially due to their formatting and reasoning steps, which makes multistep traces a bit tricky to navigate. Is there a recommended way in Phoenix to control or filter the trace data more selectively? I鈥檓 particularly interested in logging or visualizing only the most relevant traces to our workflow. Would really appreciate any tips or best practices for keeping trace logs clean and easy to work with. Thanks!
