Dokploy / Dokploy/dokploy

Log viewer incorrectly displaying error log level when error log level is not used

Open
#1,996 7 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

To Reproduce

My guess is it's doing this because the log message includes the word "failed" in it.

Here's my evidence from Dokploy log viewer:

Image

You can see the red coloured line displays as an error.

However, the java code for this message uses log level info. Additionally, I've cross-refenced this log in Grafana and it displays correctly in that. See below Java code and Grafana logs screenshots.

Image

Image

Current vs. Expected behavior

Currently a log with level info have the word "failed" in its message displays as an error log in the Dokploy log viewer.

It should display as log level info, regardless of what words exist in its log message.

Provide environment information
Not relevant in this case, but, 

Dokploy Cloud
Hetzner
amd64, 4 CPU, 8GB RAM
Debian 12
Docker Compose running Java Spring Boot service with JRE 17
Which area(s) are affected? (Select all that apply)

Cloud Version, Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Additional context

My guess is it's doing this because the log message includes the word "failed" in it.

Will you send a PR to fix it?

Maybe, need help

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 tracing the Dokploy log viewer's log-level classification and compare the parsed level with message-text matching. Reproduce the case using an info-level message containing "failed", then verify that the viewer preserves the info level regardless of message wording. No source file or test is named, so locating the relevant entry point and adding coverage will require repository research.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, java, spring-boot, typescript
Domain
frontend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.