As I move stories into production I’m realising I need better visibility into what’s happening. I want to be able to see when a story ran, what events it processed, whether anything failed, and how long things took. What tools does Tines give you for monitoring and auditing story execution?
Tines has built-in story run history and event logs accessible directly from the storyboard. Each action shows a log of recent events, including the full output data, which makes it straightforward to trace exactly what happened during any given execution. I highly recommend using routes and the Show this run’s events only option - they are game changers for troubleshooting!
At the story level, the runs view (found in the top right corner, see screenshot below) gives you a timeline of recent executions with status, duration, and timestamps. This is useful for confirming a scheduled story fired when expected, checking how long a workflow is taking end to end, and spotting patterns in failures over time.
Story run data can also be exported via the Tines API, making it possible to pipe execution logs into a SIEM or centralized logging platform for longer-term retention and reporting, if that is desired.