-
🔍 Check for existing issues
How is Dozzle deployed?Agents 📦 Dozzle version10.0.6 ✅ Command used to run Dozzlen/a 🐛 Describe the bug / provide steps to reproduce itThe statistics/counter for notifications / alerts do not update on the web UI. This is despite alerts being successfully sent, in relation to 1 or more containers. 💻 EnvironmentDocker, Debian 13 host 📜 Dozzle logs are required for debugging purposes. You may need to enable debug mode. See https://dozzle.dev/guide/debugging.📸 If applicable, add screenshots to help explain your bugAlerts work properly:
But the UI counters do not update to reflect sent alerts, even after page reload and container restart:
|
Beta Was this translation helpful? Give feedback.
Answered by
mitchplze
Mar 9, 2026
Replies: 11 comments 3 replies
-
|
Hmm. I would expect to logs to show a trigger.
But I don't see that in the logs. What's happening? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Try latest version. Might have been fixed. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Issue is not resolved in v10.1.0 
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Did you have a log like that? To be clear, alert stats are not stored to disk. Between restarts, it goes away. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Stats do not populate for me, ever, even without restarting. Here is the most recent fresh debug log run. Many notifications pushed, UI still shows 0/0 even after hard browser reload. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I expect to see something logging the matched subscription. And I haven't been able to reproduce it. I see statistics just fine. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don't know what else to say. Destination shows and tests out okay. Alert stats never update. Alerts are never logged. Below log includes me using the 'test' destination button, resaving the alert profile etc., with the sample Falco alert turned on (fires several times a minute at least). I'm not doing anything strange that I'm aware of. dozzle:
image: amir20/dozzle:latest
container_name: dozzle-master
mem_limit: 512M
restart: unless-stopped
environment:
DOZZLE_LEVEL: debug
DOZZLE_ENABLE_ACTIONS: true
DOZZLE_ENABLE_SHELL: true
DOZZLE_REMOTE_AGENT: "a.example:7007,b.example:7007"
DOZZLE_AUTH_PROVIDER: forward-proxy
DOZZLE_AUTH_HEADER_USER: X-Forwarded-User
DOZZLE_AUTH_HEADER_EMAIL: X-Forwarded-Email
DOZZLE_AUTH_HEADER_NAME: X-Forwarded-Preferred-Username
volumes:
- ./data:/data
# ports: # pushed through an OIDC proxy
# - 9999:8080
healthcheck:
test: ["CMD", "/dozzle", "healthcheck"]
interval: 10s
timeout: 30s
retries: 5
start_period: 30s |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I think that's what it is. You are using agents. |
Beta Was this translation helpful? Give feedback.
-
|
I'll convert this to a discussion. Maybe other people can help reproduce it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@mitchplze are these alerts running on agents? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Not sure how the notification architecture works - but yes - I’m using agents everywhere, including the server itself. As the alerts (setup on the server) do actually seem to work - this would seem to be a ui reporting issue. Are you saying alerts shouldn’t work on remote? |
Beta Was this translation helpful? Give feedback.
-
|
No. I think I know the issue. I was only testing with a single instance. Agents work too. But the stats are only local to the agent. They don't get reported back. Which explains what you are seeing. I'll have to see if it is easy to do that because there is performance complications if I have to load the stats every time. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
mitchplze
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#4524