Dokploy / Dokploy/dokploy

Advanced Request/Response Logging with App and Env Filtering

Open
#4,867 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Currently, the request logging capabilities in Dokploy are very basic. For production-grade monitoring and debugging, it is difficult to isolate and analyze HTTP traffic because we cannot filter the requests. Additionally, critical debugging data such as request/response headers and detailed payloads are missing from the current view, forcing developers to manually inspect container logs for HTTP issues.

Describe the solution you'd like

I would like to see an enhanced Requests section with the following features:

Advanced Filtering: The ability to filter the request logs by a specific Application and Environment (e.g., Production, Staging).

Detailed Inspection: Clicking on a specific request should display a detailed breakdown containing:

Full Request & Response Headers.

Request/Response body payloads (where applicable).

Request latency/execution time and client IP/User-Agent details.

Describe alternatives you've considered

An alternative is setting up external logging and APM tools (like OpenTelemetry, Better Stack, or self-hosted Signoz/Grafana Loki) inside the containers. However, this adds architectural complexity and resource overhead for projects that just need quick, native HTTP traffic debugging directly within the Dokploy dashboard.

Additional context

This feature could potentially leverage the existing Traefik/Proxy log middleware data and present it in a searchable table. To avoid heavy database writes or performance issues, this detailed logging could be made optional (opt-in) per application, so users can enable it only when debugging.

Will you send a PR to implement it?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing Requests section and tracing how Traefik/Proxy middleware log data currently reaches the dashboard. Done should include Application and Environment filtering, request detail views with the listed headers, payloads, latency, and client metadata, plus an optional per-application logging mode that avoids unnecessary writes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.