# Suppress individual trial output
**URL:** https://discuss.ray.io/t/suppress-individual-trial-output/6191
**Category:** Ray Tune
**Created:** [May 19, 2022, 3:21pm UTC](https://discuss.ray.io/t/suppress-individual-trial-output/6191 "2022-05-19T15:21:06Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@krafczyk](https://discuss.ray.io/u/krafczyk)
#### Post date: [May 19, 2022, 3:21pm UTC](https://discuss.ray.io/t/suppress-individual-trial-output/6191/1 "2022-05-19T15:21:06Z")
**How severe does this issue affect your experience of using Ray?**
- Low: It annoys or frustrates me for a moment.
When I run a tune functional API search, I’m finding that stdout from each trial is landing in the shell I originate the trial from. This is great for debugging, and I can use log\_to\_file to send the stderr/stdout to files. But when I run large scale experiments, I may have many trials running simultaneously and the terminal is flooded with text. Is there a way to use log\_to\_file but also suppress stderr/stdout of each trial (unless there’s an error), and then only show the progress of the various trials like it usually does.
---
### Author:  [@ericl](https://discuss.ray.io/u/ericl)
#### Post date: [May 19, 2022, 9:19pm UTC](https://discuss.ray.io/t/suppress-individual-trial-output/6191/2 "2022-05-19T21:19:53Z")
Hey @krafczyk , you can disable Ray logging to the driver with `ray.init(log_to_driver=False)`. That will suppress log routing to the shell, but will not otherwise affect Tune status reporting, etc.