Uptime-kuma baremetal
Im running uptime-luma baremetal from proxmox helper scripts. Can my acquis.yaml look like this?
I can see that my parser is getting stuff, but its not banning any

19 Replies
Important Information
This post has been marked as resolved. If this is a mistake please press the red button below or type
/unresolve
Β© Created By WhyAydan for CrowdSec β€οΈ
Most likely it should be
syslog
to strip the prefix and then syslog parser will set the program to uptime-kuma
for the next stage.
plus also the service is writing the logs as npm
and not uptime-kuma
instead of journalctl?
So did you create a systemd service?
Yea, there is one π
can you
systemctl cat uptime-kuma.service
and provide it
Can you run
sudo systemctl edit uptime-kuma
to create an override file
then add these contents:
like this right? π

Yes
then you must run:
Done π
Now if you get the logs the name should be correct and not
npm
Cool! yes, that correct

Then change the
type
to syslog
in acquisition and it should be magic after reload?Thank you so much, working great!!
So a tldr; by default if there is no identifer it will default to process name as
npm
to work with journalctl the name has to be what the parser expect so an override is needed in this case.Learning new things everyday. Thank you for being so helpful ππ½
Resolving Uptime-kuma baremetal
This has now been resolved. If you think this is a mistake please run
/unresolve