LogDirectoryPath
Contents
[
Hide
]
LogDirectoryPath is the file path where the native logger writes output. Despite the name, the value is a full file path — not a directory.
Quick reference
| Type | string |
| Default | "logs/log.txt" |
| Category | Engine |
| Field on | EngineParameters.LogDirectoryPath |
What it does
When the native logger writes (mostly when EnableDebugLogging is true), output goes to this file. If the file does not exist, it is created; if it does, output is appended.
- Default
logs/log.txt— a filelog.txtinside alogsfolder, resolved relative to the current working directory. - Absolute path — write to a specific location regardless of working directory.
When to change it
| Scenario | Value |
|---|---|
| Default | "logs/log.txt" |
| Per-environment log file | "logs/staging.log", "logs/prod.log" |
| Centralized logging location | "/var/log/aspose-llm/app.log" |
| Working directory is not writable | Absolute path to a writable folder |
Example
var preset = new Qwen25Preset();
preset.EngineParameters.EnableDebugLogging = true;
preset.EngineParameters.LogDirectoryPath = "/var/log/aspose-llm/app.log";
using var api = AsposeLLMApi.Create(preset, logger);
Ensure the parent directory exists and the process has write permission:
var logFile = "/var/log/aspose-llm/app.log";
Directory.CreateDirectory(Path.GetDirectoryName(logFile)!);
preset.EngineParameters.LogDirectoryPath = logFile;
Interactions
EnableDebugLogging— the main switch for output that this file receives.ILoggerpassed toAsposeLLMApi.Create— complementary managed-side logging.
What’s next
- Logging and diagnostics — full logging reference.
- Engine parameters hub — all engine knobs.