There is no trace logger.

At the moment there is no easy way to monitor trace messages from the devices but the users would need this information to verify the behaviour of the device and perhaps to manually test it. Messages from device logger, produced by statements in the device code, could be redirected to the screen through a log viewer that presents them in the dashboard as text messages . Adherence to the standard behaviour of loggers would be good: we can expect different log levels (FATAL, INFO, TRACE, DEBUG,...), different formats of messages and different sinks. Moreover, some of this info could be specified in a configuration file. The currently adopted workaround was to define a Tango activity attribute where the log messages from the devices are stored and to let Taurus read and display that attribute in a text box.

This issue might be tackled relatively soon (even next week!). At the moment however no plan has been made: the team will decide after hearing the opinion of the MaxIV team.