Feature Request: Adjust console log output to match correctly

Open

#2,922 opened on Oct 30, 2025 0 comments 1 reaction 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?

As you can see in the above image, this is a stack trace and is part of one single strign separated by new line characters that get mistaken as a new log entry. Most of the time logs can be difficult to read and sift through due to dokploy flagging entries as an error when it isn't

Describe the solution you'd like

For console log entries to be categorised correctly either by a custom regex or other solution

Describe alternatives you've considered

N/A

Additional context

No response

Will you send a PR to implement it?

Contributor guide

Open the contributing guide

First steps

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

Research direction

The issue does not name any files, tests, or entry points. Start by locating the console-log parsing and categorization flow, then establish how multiline stack traces should be recognized and what output should count as done; the issue currently leaves the implementation approach and acceptance criteria open.

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: Stale
Clarity: Needs clarification
Newbie friendliness: 25/100

A short digest of beginner-friendly GitHub issues.