Metrics doesn't update and generates a console error
Closed this issue · 7 comments
Steps to reproduce
Go to Server -> Metrics.
Expected behavior
Metrics are up to date, no console errors.
Actual behavior
I get a 404 error for /actuator/metrics/komga.sidecars. Metrics do not update unless I take the docker container down then bring it back up.
Logs
Going to the metrics page generates a 404 on /actuator/metrics/komga.sidecars in the console.
Server logs generate:
2024-08-04T01:38:03.436-04:00 WARN 1 --- [http-nio-25600-exec-1] o.s.web.servlet.PageNotFound : No mapping for GET /settings/metrics
for each visit.
Going to /actuator/metrics generates this JSON:
{
"names": [
"application.ready.time",
"application.started.time",
"disk.free",
"disk.total",
"executor.active",
"executor.completed",
"executor.pool.core",
"executor.pool.max",
"executor.pool.size",
"executor.queue.remaining",
"executor.queued",
"hikaricp.connections",
"hikaricp.connections.acquire",
"hikaricp.connections.active",
"hikaricp.connections.creation",
"hikaricp.connections.idle",
"hikaricp.connections.max",
"hikaricp.connections.min",
"hikaricp.connections.pending",
"hikaricp.connections.timeout",
"hikaricp.connections.usage",
"http.server.requests",
"http.server.requests.active",
"jdbc.connections.active",
"jdbc.connections.idle",
"jdbc.connections.max",
"jdbc.connections.min",
"jvm.buffer.count",
"jvm.buffer.memory.used",
"jvm.buffer.total.capacity",
"jvm.classes.loaded",
"jvm.classes.unloaded",
"jvm.compilation.time",
"jvm.gc.concurrent.phase.time",
"jvm.gc.live.data.size",
"jvm.gc.max.data.size",
"jvm.gc.memory.allocated",
"jvm.gc.memory.promoted",
"jvm.gc.overhead",
"jvm.gc.pause",
"jvm.info",
"jvm.memory.committed",
"jvm.memory.max",
"jvm.memory.usage.after.gc",
"jvm.memory.used",
"jvm.threads.daemon",
"jvm.threads.live",
"jvm.threads.peak",
"jvm.threads.started",
"jvm.threads.states",
"komga.books",
"komga.books.filesize",
"komga.collections",
"komga.libraries",
"komga.readlists",
"komga.series",
"komga.tasks.execution",
"komga.tasks.failure",
"logback.events",
"process.cpu.usage",
"process.files.max",
"process.files.open",
"process.start.time",
"process.uptime",
"spring.security.authentications",
"spring.security.authentications.active",
"spring.security.authorizations",
"spring.security.authorizations.active",
"spring.security.filterchains",
"spring.security.filterchains.access.exceptions.after",
"spring.security.filterchains.access.exceptions.before",
"spring.security.filterchains.active",
"spring.security.filterchains.authentication.anonymous.after",
"spring.security.filterchains.authentication.anonymous.before",
"spring.security.filterchains.authentication.basic.after",
"spring.security.filterchains.authentication.basic.before",
"spring.security.filterchains.authentication.rememberme.after",
"spring.security.filterchains.authentication.rememberme.before",
"spring.security.filterchains.authorization.after",
"spring.security.filterchains.authorization.before",
"spring.security.filterchains.context.async.after",
"spring.security.filterchains.context.async.before",
"spring.security.filterchains.context.holder.after",
"spring.security.filterchains.context.holder.before",
"spring.security.filterchains.context.servlet.after",
"spring.security.filterchains.context.servlet.before",
"spring.security.filterchains.cors.after",
"spring.security.filterchains.cors.before",
"spring.security.filterchains.header.after",
"spring.security.filterchains.header.before",
"spring.security.filterchains.logout.after",
"spring.security.filterchains.logout.before",
"spring.security.filterchains.requestcache.after",
"spring.security.filterchains.requestcache.before",
"spring.security.filterchains.session.concurrent.after",
"spring.security.filterchains.session.concurrent.before",
"spring.security.filterchains.session.management.after",
"spring.security.filterchains.session.management.before",
"spring.security.filterchains.session.urlencoding.after",
"spring.security.filterchains.session.urlencoding.before",
"spring.security.http.secured.requests",
"spring.security.http.secured.requests.active",
"spring.security.http.unsecured.requests",
"spring.security.http.unsecured.requests.active",
"system.cpu.count",
"system.cpu.usage",
"system.load.average.1m",
"tasks.scheduled.execution",
"tasks.scheduled.execution.active",
"tomcat.sessions.active.current",
"tomcat.sessions.active.max",
"tomcat.sessions.alive.max",
"tomcat.sessions.created",
"tomcat.sessions.expired",
"tomcat.sessions.rejected"
]
}Console shows:
The connection to (server)/sse/v1/events was interrupted while the page was loading. app.19e604c6.js:1:36912
Komga version
1.11.2-master
Operating system
Ubuntu 24.04 LXC on Proxmox 8 host
Installation method
Docker
Other details
No response
Acknowledgements
- I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
- I have written a short but informative title.
- I have checked the FAQ.
- I have updated the app to the latest version.
- I will fill out all of the requested information in this form.
do you even have sidecars?
do you even have sidecars?
I'm sorry, I don't know what that is. I installed it using the docker compose from this page. If it's a dependency, shouldn't it be included?
it's unclear what your problem is, is it only errors in the javascript console, or some errors in the webpage ?
it's unclear what your problem is, is it only errors in the javascript console, or some errors in the webpage ?
Yes, sorry. The 404 error for /actuator/metrics/komga.sidecars is in the javascript console in browser and the metrics page is not updated. The only time the page is updated is when I restart the docker container but then it's stuck again with the 'updated info'.
The page itself is fine, just with outdated data that is never updated.
and the metrics page is not updated.
what does that mean ? can you clarify ?
and the metrics page is not updated.
what does that mean ? can you clarify ?
This page is never changed no matter how many files I delete or add until I restart the docker container. If I do that, it will update then stay the same again even if I delete or add files.
🎉 This issue has been resolved in 1.11.3 (Release Notes)