Log files

The program logs of Studio and Live (the logs folder), the project's event log and the Event view, what is written, how long it is kept, and what to collect for support.

Two separate kinds of log

FabyaVision writes two different things; do not confuse them.

Program log (logs folder)

Each program writes one file per day to the logs subfolder in its own folder. In a default installation the path is C:\Program Files\Fabyatek\FabyaVision\Studio\logs and …\Live\logs; the installation allows normal users to write to these folders. Files whose last modification date is older than 30 days are deleted every time the program is opened. Uninstalling the program also deletes the logs folders; if a problem is being investigated, copy the logs first.

Each line starts with a timestamp: 2026-10-17 09:30:12.345 ileti (year-month-day hour:minute:second.millisecond, followed by two spaces). The file is UTF-8. A log that cannot be written does not stop the program; the write error is silently ignored.

Opening the folder

1

1. Open log folder — opens the logs folder in Windows Explorer.

• Studio: Help›Open log folder. The command opens the folder in Windows Explorer. It works only inside the Studio program; Studio opened in a browser cannot do this and shows an information window.
• Live: Live does not have this command. Open the Live\logs folder yourself in File Explorer (default: the program folder, see Files and folders of Live).

What gets written

Line texts are written without Turkish characters (e.g. baslatilamadi). Look for the following starting patterns.

Event log

The event log belongs to the project: while Live is running, it appends events to the file <Ad>.veri\gunluk\olay_yyyyMM.log (the month is the local month at the moment the record is written). The file is UTF-8; each line is a single-line JSON record:

{"z":1760689812345,"t":"betik","k":"operator1","m":"Tank_Seviye_Denetimi / Yok_Boyle_Prosedur: \"Yok_Boyle_Prosedur\" prosedürü bulunamadı"}

z

Time: Unix milliseconds.

t

Type ID: oturum, ayar, recete, rapor, sistem, betik, operator.

k

The user who was logged on at the time of the record (empty if none).

m

Text.

d

Optional detail: for value writes, the tag, the old and new value and the result; for connection events, the connection name and the error.

Connection events are stored in the file with the type sistem and with the connection information in the d field; the Event view shows them as a separate Connection type.

Event types

Event view object

123

1. Type filter — Session, Setting, Recipe, Report, System, Script, Connection.
2. Script error — script / procedure, message.
3. System record — Live has started.

• The Current view shows the records of the session and the last 1000 records of the log; a new event is added at the top of the list.
• The History view reads Today, Yesterday, Week, Month, All or a manually entered date range; at most the last 20000 records are shown.
• There are type buttons, user and text search, and paging. Excel saves the entire filtered list as olay_gunlugu_….xlsx (Time, Type, User, Text, Tag, Old value, New value, Result, Source).
• The object shows the types selected by the project designer; a type may be hidden on the screen. If the file contains the entry but the object does not show it, check the object's type selection.

How frequently written entries are limited

• Trace and printf output: the same text is written to the event log only once every 10 seconds.
• Script errors and warnings: the same text is written once per 60 seconds; the repetitions in between are counted in the next entry as (+N kez). JavaScript errors are not limited.
• Connection events: a state that lasts at least 2 s is written; if there are more than 5 changes within 60 s, a single Connection unstable entry is written (Connection problems).

Information to collect for support

1. Describe the problem

   What you did, what you expected, what happened; when the problem started. If possible, write the date and time: this is where to look in the log.

2. Obtain the program logs

   The Live_yyyyMMdd.log file of the day with the problem and, if needed, the Studio_yyyyMMdd.log file. For Live startup problems, the first lines of the log (WebView2 version) are important.

3. Obtain the event log

   The olay_yyyyMM.log file of the month with the problem, or the Excel export from the Event view. It is the most informative file for script and connection problems.

4. Add the project file

   .fvs file. It may contain connection addresses and user information; consider who will see it before you share it.

5. Version and environment information

   In Studio, Help›About FabyaVision gives the version. The WebView2 version is in the first line of the program log. State the Windows version and the display configuration of the computer on which Live runs (multiple displays, TV).

6. Screenshot

   An image showing the error message and the Connections section of the system menu; in Live the screenshot key can also be used (Live settings).