Kamal: Created page with "The Charting Server processes time series queries on market data and publishes ongoing updates to clients. It performs calculations such as candlestick aggregation, technical..."

2026-05-27T20:02:09Z

Created page with "The Charting Server processes time series queries on market data and publishes ongoing updates to clients. It performs calculations such as candlestick aggregation, technical..."

New page

The Charting Server processes time series queries on market data and publishes ongoing updates to clients. It performs calculations such as candlestick aggregation, technical indicators, and other analytical transformations over historical and real-time market data. By centralizing these computations, the server enables multiple clients to subscribe to identical chart data without redundant calculation overhead.

The Charting Server integrates with the [[Service Locator]] for authentication and service registration. Multiple Charting Servers can be deployed concurrently to distribute query processing load across instances, with the Service Locator performing the load balancing among them.

== Configuration ==

The Charting Server is configured via a YAML file with two top-level sections: <code>server</code> and <code>service_locator</code>. Below is the structure of the configuration file with example values:

<pre>
server:
# Primary network interface and port the Charting Server binds to.
interface: "0.0.0.0:21400"
# List of addresses the server is reachable at (for registration with Service Locator).
# Typically includes both public-facing and local addresses.
addresses: ["198.51.100.5:21400", "10.0.0.5:21400"]

service_locator:
# The address of the Service Locator (host:port).
address: "10.0.0.5:20000"
# The account username used by the Charting Server to authenticate with the Service Locator.
username: charting_server
# The password for the Charting Server's Service Locator account.
password: [REQUIRED]
</pre>

A <code>setup.py</code> script is provided to generate the final <code>config.yml</code> from the <code>config.default.yml</code> template. Usage:

<pre>
--local 0.0.0.0 # Local interface (default: auto-detected IP)
--world 198.51.100.5 # Global/public interface (optional)
--address 10.0.0.5:20000 # Service Locator address (default: local_interface:20000)
--password [REQUIRED] # Service password for authentication
</pre>

== Management ==

The Charting Server is controlled using three operational scripts: <code>start.sh</code>, <code>stop.sh</code>, and <code>check.sh</code>.

=== start.sh ===

* Exits immediately if the server is already running.
* Creates a <code>logs/</code> directory if necessary.
* Moves any existing <code>srv_*.log</code> files into <code>logs/</code>.
* Starts the <code>ChartingServer</code> process in the background.
* Reads network interfaces from <code>config.yml</code> and waits until the server is listening on at least one configured address.

This ensures the server is fully initialized before the script exits.

=== stop.sh ===

* Sends <code>SIGINT</code> to request a graceful shutdown.
* Waits for termination using exponential backoff (up to 300 seconds).
* Sends <code>SIGKILL</code> if the server fails to stop cleanly.
* Appends a forced-termination message to the most recent log file (if applicable).

This guarantees consistent shutdown behavior across normal and exceptional conditions.

=== check.sh ===

The <code>check.sh</code> script verifies whether the server is currently running by inspecting the PID recorded in <code>pid.lock</code> and testing whether the associated process exists.

== Logging ==

Upon startup, older log files are moved into the <code>logs/</code> directory.

Charting Server - Revision history

Kamal: Created page with "The Charting Server processes time series queries on market data and publishes ongoing updates to clients. It performs calculations such as candlestick aggregation, technical..."