Log Sources

By default Runeya reads the output of the process it starts. This is the console source, and it is always on. Add another source when the service writes its logs somewhere else, such as a file or a table.

Adding a source

In the service's configuration, Log sources tab, add a source and pick its type. All lines appear in the same stream, and each line shows which source it came from.

A source collects only while the service runs. Removing it stops collection without erasing what is already displayed.

File

A relative path starts from the service's working directory (for example logs/app.log). Prefer it over an absolute path: the service keeps the same setting on every machine, even when the project is stored in a different place.

Two options change the behavior at startup:

• Start from the end (default): only new lines come through. Uncheck it to replay the file from the beginning.
• Create file if not exists: Runeya creates the file if it is missing. Without this option, the source fails.

MongoDB

Connection string, database and collection. Runeya polls the collection and reads the new documents. Set the names of the fields to read: timestamp, message, and level if you have one.

MySQL

Host, credentials, database and table, with the matching columns. A SQL query can replace reading the table directly. Polling runs every 2 seconds by default, so a new line can take up to 2 seconds to appear.

What usually goes wrong

Symptom	Usual cause
Nothing from a file	Relative path, missing file, or no read permission
A file shows only new lines	"Start from the end" is on
A database returns nothing	The service is not running, or the timestamp field is not the one declared
A few seconds of delay	The polling interval. This is expected.

Connection credentials are treated as secrets. They are stored encrypted, never shown in clear and never written to the logs.