kuma's certificate monitoring problem

[lsx1205]

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Is there a way for kuma to configure it to monitor only the certificate expiration time and not the website itself? Because the site has many sites, it is possible that only one site is unavailable, not all of them

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

rocky linux 9.4

🌐 Browser

google chrome

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors:

[lsx1205]

Is this heartbeat interval related to certificate monitoring? Is certificate monitoring updated once the heartbeat is performed? Or does the heartbeat have nothing to do with certificate monitoring, and an alarm is generated when the alarm period reaches?

[lsx1205]

Another question is whether kuma's logs can be mounted externally when using docker containers. Otherwise it is not very convenient to clean the log, or does kuma have a built-in log cleaning function?

[CommanderStorm]

configure it to monitor only the certificate expiration time and not the website itself?

To monitor a certificate, we need to look at a website. I don't know what you are asking, but getting certificates from websites without asking the website for certificates is impossible.

Because the site has many sites, it is possible that only one site is unavailable, not all of them

We have group monitors available which function via the any(monitor.status == DOWN for monitor in monitors) method if that is what you are asking.
I don't see a problem with having more monitors (up to the scaling limit, see #4500)

[CommanderStorm]

Is this heartbeat interval related to certificate monitoring? Is certificate monitoring updated once the heartbeat is performed? Or does the heartbeat have nothing to do with certificate monitoring, and an alarm is generated when the alarm period reaches?

Certificates get checked on every heartbeat if the option is enabled.
Checking them is extremely cheap on modern hardware => no need to optimised this part

[CommanderStorm]

Another question is whether kuma's logs can be mounted externally when using docker containers. Otherwise it is not very convenient to clean the log, or does kuma have a built-in log cleaning function?

Which path did you deploy with? (Node vs docker)
You left that field blank.

Docker logs to standard out and is collected via the default driver. You can access logs via docker logs .... Said driver by default rotates logs.
For pm2, please see our wiki how to set up pm2-logrotate.