Where to find log files persisted to disk / volumes for fault finding
Are you finding yourself in a scenario where you are struggling to get a Timebase component to start up? The reason might be logged in the log files, but you can't access the status page of the component as it is not running.
Log files are also persisted to disk, so you would be able to get the possible errors and warnings on component startup logged to disk.
Where to find these files? Well, dependant on the architecture, it will be located in different locations
Windows Installation
For Windows: All log files will located, by default, in the following locations:
Collector
C:\ProgramData\Flow Software\Timebase\Collector\Logs
Explorer
C:\ProgramData\Flow Software\Timebase\Explorer\Logs
Historian
C:\ProgramData\Flow Software\Timebase\Historian\Logs
Pulse
C:\ProgramData\Flow Software\Timebase\Pulse\Logs
Service Starter
C:\ProgramData\Flow Software\Timebase\Service Starter\Logs
Remember: Based on your server starter configuration, these default location might change. Make sure to reference the location based on your service starter configuration
Docker Implementation
Based on your Docker Compose .yml file, volumes would be attached to each service in your stack. An example of a volume configuration would be:
volumes:
- explorer:/explorer
environment:
- Settings=/explorer/settings
- Config=/explorer/config
- Data=/explorer/data
- Logs=/explorer/logs
All log files will be logged in the specified volume defined. These can be accessed either inside the container or on the host:
Remember: Best practise is always to use Volumes to persist data and config for your Docker containers. These might change from our default examples based on your specific docker rollout.