Services
Overview
The Services settings page provides technical information about the services that are registered and interact with your CAST Imaging installation, and lets you download their logs. It has two tabs: Services and Logs.


Services tab
Lists each component registered with your CAST Imaging installation:
analysis-nodesimaging-servicesAvailable in ≥ 3.6.8-funcrelimaging-viewerdashboards
analysis-nodes
For each node that is registered with your CAST Imaging installation, an entry will be listed. This typically takes the following format:

Name / URL / technical spec

Display name, URL and technical spec of the registered node. The name is determined automatically and consists of the server host name/IP address as defined during the installation and the port that the node service is running on.
The display name for the node can be customized as part of the installation process for Linux via Docker, via the IMAGING_NODE_INSTANCEID variable available in the configuration.conf properties file.
Disk and database storage status

Shows:
- the status of the disk storage on the node. Rolling the mouse pointer over the icon will display the amount of free disk space in GB. The icon will be displayed in yellow when disk space is low.
- the status of all PostgreSQL instances (whether it is “up” (green) or “down/unreachable” (red)) configured in CAST Imaging (see CSS and Measurement settings). Rolling the mouse pointer over the icon will display the host name and port number of the instance.
Service logs
From 3.6.9-funcrel, this panel is no longer displayed: download node logs from the Logs tab.
In earlier releases, use this panel to download the logs of the node service for the current node - on Microsoft Windows, the %PROGRAMDATA%\CAST\Imaging\CAST-Imaging-Analysis-Node\logs\analysis-node.log file. The panel was labelled System Logs in releases before 3.6.8-funcrel.
imaging-services / imaging-viewer / dashboards
Shows the status of each of these components, with imaging-viewer and dashboards also showing the URL and port number of the service. Expand an entry to see the services it is composed of. Where a service is uncontactable, it is displayed in red:

To download the logs of these services, use the Logs tab.
Logs tab
Downloads the logs of every service listed on the Services tab:

- Choose a date range of up to 31 days with the From and To dates, or select one of the presets Today, Last 7 days or Last 31 days. The range applies to every log you download.
- Select the logs you need. Selecting a component selects all of its services, and the checkbox in the Service header selects every log on the page.
- Select DOWNLOAD. The button shows how many logs are selected. When you select several logs, they arrive as a single ZIP file containing one folder per service.
To download a single log without selecting it, use the download icon at the end of its row.
| Component | Services whose logs you can download |
|---|---|
analysis-nodes |
One entry per registered node |
imaging-services |
Control Panel, Gateway, Auth Service, Console, SSO |
imaging-viewer |
Imaging Viewer, ETL, Imaging API, AI Service, Neo4j |
dashboards |
The dashboards service |
As soon as you select a log, a bar above the list shows how many are selected, with Select all and Clear selection shortcuts:

When the download completes, a message confirms how many logs were downloaded and the selection is cleared. Select DISMISS to close the message:

See Microsoft Windows file storage locations and Linux via Docker/Podman file storage locations for where each service writes its logs on disk, and how long they are kept.
Download service logs in 3.6.8-funcrel
In 3.6.8-funcrel, there is no Logs tab: logs are downloaded one service at a time from a panel on the Services tab. In releases before 3.6.8-funcrel, only the analysis node service offered a log download - see Service logs.
Expand the component you are interested in, then expand the service whose logs you need. Each service carries a Service logs panel: choose a From and a To date, and select DOWNLOAD.


The logs arrive as a ZIP file named for the service and the range you chose, for example:

Where the service wrote nothing in that range, no file is produced and a message is displayed instead:
