Traefik Access Log Parsing#

Dokploy reads Traefik's JSON-format access logs from disk and exposes a filtered, paginated view in the Requests dashboard tab. This is entirely server-side: the raw log file is read on each API call, filtered in memory, and the result set is returned — no database is involved.

Log File Location & Reading#

readMonitoringConfig in packages/server/src/utils/traefik/application.ts reads the log file at:

${DYNAMIC_TRAEFIK_PATH}/access.log

• Production: /etc/dokploy/traefik/dynamic/access.log
• Development: .docker/traefik/dynamic/access.log

When no date-range filter is active, it streams the file and returns the first 500 valid JSON lines to avoid loading the entire file into memory 1. When a date range is provided, readAll=true is passed and the full file is read 2.

Internal dashboard traffic is excluded at read time: lines with ServiceName === "dokploy-service-app@file" are skipped 3.

LogEntry Schema#

Each log line is parsed into a LogEntry object (packages/server/src/utils/access-log/types.ts). Key fields used in filtering and display:

Parsing & Filtering Pipeline#

parseRawConfig in packages/server/src/utils/access-log/utils.ts applies filters in this order:

1. JSON validation — splits on newlines, keeps only lines that start with { and end with } 4
2. Internal service exclusion — drops dokploy-service-app@file entries 5
3. Date range — compares log.StartUTC against optional start/end ISO strings 6
4. Hostname search — case-insensitive substring match on log.RequestHost 7
5. Status filter — maps named buckets (info, success, redirect, client, server) to HTTP status ranges via isStatusInRange 8
6. Sort — _.orderBy on any LogEntry field; defaults to time desc 9
7. Pagination — slice by pageIndex * pageSize 10

Returns { data: LogEntry[], totalCount: number }.

Note: totalCount reflects the post-filter, pre-pagination count, so the UI can compute page counts correctly.

Hostname Filtering Fix (PR #4255)#

Prior to PR #4255, the search filter matched against RequestPath (the URL path) instead of RequestHost. The fix updated parseRawConfig to use log.RequestHost and changed the UI placeholder from "Filter by name..." to "Filter by hostname..." 11.

tRPC API: settings.readStatsLogs#

The readStatsLogs tRPC procedure (protectedProcedure) wires everything together:

• Disabled in cloud mode — returns empty data when IS_CLOUD is true 12
• Accepts: page, sort, search, status[], dateRange
• Calls readMonitoringConfig then parseRawConfig and returns the result

Frontend: RequestsTable#

RequestsTable in apps/dokploy/components/dashboard/requests/requests-table.tsx consumes settings.readStatsLogs via api.settings.readStatsLogs.useQuery(...):

• Polls every 1333 ms 13
• Manages state for search, statusFilter, sorting, pagination, and dateRange 14
• Uses manual pagination (manualPagination: true) — TanStack Table defers all paging to the server 15
• Status filter options: info (1xx), success (2xx), redirect (3xx), client (4xx), server (5xx) 16
• Clicking a row opens a detail sheet; individual entries can be downloaded as JSON 17

Chart View: processLogs#

A parallel utility, processLogs, aggregates the same log data into hourly bucket counts for the chart view. It applies the same date-range and internal-service exclusion logic but does not filter by hostname or status — it simply counts entries per hour 18.

Key Source Files#