Closed jangrewe closed 5 months ago
Oh, and one little feature request: Could you change the Dockerfile from
CMD ["./main"]
to
ENTRYPOINT ["./main"]
This would allow setting any arguments like -logging.level=Warning
without having to set it to /root/main -logging.level=Warning
, as providing arguments to the container will override CMD
, but it will keep the ENTRYPOINT
.
@scross01 I think only this line needs to be changed from int64
to float64
: https://github.com/scross01/prometheus-klipper-exporter/blob/e27d9e2f0cd60f2618f6d91706fa14c8ffdff7d8/collector/history.go#L15
Thanks for finding the fix for this. I just updated my Moonraker version and see the same issue. Looks like the recent change in Moonraker caused the API to start returning a float instead of an in for the total_jobs
, probably caused by the switch from using lldb to sqlite https://github.com/Arksine/moonraker/pull/858
Fix in v0.10.3
Thanks for responding so quickly, the exporter is now running fine again!
Another issue, besides the CMD
vs. ENTRYPOINT
mentioned above: I run the exporter with
ghcr.io/scross01/prometheus-klipper-exporter:latest /root/main -logging.level=Warning
but i still get log messages for Info
- and that amount adds up quickly.
Try just
docker run ghcr.io/scross01/prometheus-klipper-exporter:latest -logging.level=Warning
or
docker run --entrypoint "/root/main" ghcr.io/scross01/prometheus-klipper-exporter:latest -logging.level=Warning
Sorry, i completely missed that you also changed CMD
to ENTRYPOINT
already, all works as expected now! 👌🏻
Hi, i've been running your exporter for quite a while (thanks for it, by the way!), but since a couple of days i'm running into this issue:
As you can see, one of the printers gets scraped successfully, but then second one runs into an error.
My Prometheus scrape target config follows your example, and i'm not setting any arguments besides the log level (typically Warning, but currently Info to find out what's wrong).