Closed typro33333 closed 6 months ago
From your description this could be multiple things.
What was the log output? How have you configured the monitor in terms of retention settings?
So, I will show you all my step to notification my Lark.
My Question with if gitlab uptime how uptime kuma send custom another notification uptime to bot ?
So we are talking about two differnt things. Your inital message gave the impression that NO allert is send out on a monitor coming UP
but when services up, it not alert again
You are talking about something different in the second message.
Finally, it sent again downtime notification
This is because you have configured the webhook to open the issue in larksuite.
Said webhook is send on both DOWN
/UP
/Certificate Expiry/Testing.
Currently, filtering what notifications get passed to which notification provider is not supported.
See https://github.com/louislam/uptime-kuma/issues/508 for the tracking issue
Please see https://github.com/louislam/uptime-kuma/issues/3715 for how to configure Lark via Feishu
as the notification type or how to contribute a dedicated notifiaton type for Lark ^^
Thanks so much for answer to help me.
⚠️ Please verify that this question has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
I have setup notify check healthy my gitlab server. Also i have setup notify webhook through to Lark Suite. It has sent alert when services down but when services up, it not alert again.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Ubuntu 20.04
🌐 Browser
Chrome
🖥️ Deployment Environment