Skip to main content
Techulus Cloud uses Victoria Logs for centralized log aggregation. All log types — container output, HTTP access logs, build logs, and agent system logs — are collected and searchable from the web UI.

​
Log Types

TypeSourceFields
containerContainer stdout/stderrdeployment_id, service_id, server_id, stream
httpTraefik access logs (proxy nodes)service_id, host, method, path, status, duration_ms, client_ip
buildBuildKit image buildsbuild_id, service_id, project_id
agentAgent process outputserver_id, level

​
How It Works

Each agent ships logs directly to Victoria Logs over HTTP using the JSON Lines format.
  • Container logs are streamed from running containers, batched in groups of 1000, and flushed every 5 seconds. Log positions are tracked per container to prevent duplicates.
  • HTTP logs are tailed from Traefik’s access log file on proxy nodes, batched in groups of 500.
  • Build logs are captured during image builds and streamed in real time.
  • Agent logs intercept the agent’s own stdout/stderr with automatic log level detection.
All log batches retry up to 3 times with exponential backoff on failure.

​
Configuration

Victoria Logs runs as a Docker container alongside the control plane.
VariableDescription
VL_USERNAMEAuthentication username
VL_PASSWORDAuthentication password
VL_RETENTIONLog retention period (default: 7d)
The control plane exposes logs at https://logs.<ROOT_DOMAIN> with basic auth. Agents write to the internal endpoint at http://victoria-logs:9428.

​
Accessing Logs

Logs are accessible from the web UI for each service, deployment, build, and server. The control plane queries Victoria Logs using LogSQL with filters for service_id, deployment_id, server_id, and time ranges.