Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option for notification on message change #2053

Open
1 task done
mtelgkamp opened this issue Sep 8, 2022 · 6 comments
Open
1 task done

Option for notification on message change #2053

mtelgkamp opened this issue Sep 8, 2022 · 6 comments
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added

Comments

@mtelgkamp
Copy link
Contributor

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

New Notification, Other

🔖 Feature description

If you have a monitor and it is down, it might be interesting to see a change of the message / Problem.

Example 1: Push monitor, changes the error message
Example 2: HTTPS monitor, changes from DNS Problem to Status 50X problem

✔️ Solution

I would like to have an option to be notified during down status when the message changes.
It might even be interesting to be notified on a message change during up status for example for some push monitors.

❓ Alternatives

An alternative for the push notification option would be to have multiple monitors that only look at on problem at a time.

📝 Additional Context

  • If you have a timeout notification for a monitor you might think it will be responsive again without the need to interact. If the error changes (e.g. to Error 500 on page), there will be no notification, due to the consistent down status, but it still would be good to know the change.
  • If a push monitor sends "Problem x" as message and then the message changes to "Problem x and Problem y" it might be important to get an additional notification.
@mtelgkamp mtelgkamp added the feature-request Request for new features to be added label Sep 8, 2022
@mtelgkamp
Copy link
Contributor Author

This is in some extend related to #1605 which promotes some kind of "info" or "warning" status option and the possibility to push changes in the message to the log without changing the status.

@kennyparsons
Copy link

kennyparsons commented Sep 15, 2022

👍 +1 upvoting this as well. I, however, need it for up as well. I use push monitors as a way to send bits of data periodically. Something might trigger the hook, causing the monitor to be up. But I don't know what caused the trigger from uptime-kuma's perspective, so including the msg field and triggering updates would provide this to me "at a glance."

@mtelgkamp mtelgkamp changed the title It would be nice to be notified on message change Option for notification on message change Sep 15, 2022
@projx
Copy link

projx commented Sep 16, 2022

I was just coming to request this myself - I have a cronjob that updates my DDNS, if it fails, it sends an notification via Push monitoring - But I'd also like to be able send a notification if the IP has changed, so the service is still up, but has changed..

@J-Prince
Copy link

I would also like the MSG parameter to be logged/notified when it is different from the previous one, even if status remains up.

@CommanderStorm CommanderStorm added the area:monitor Everything related to monitors label Dec 7, 2023
@Suven-p
Copy link
Contributor

Suven-p commented Oct 7, 2024

Would it be acceptable to do this independently? I am thinking by adding two checks under advanced section for "Log all events" and "Notify on all events". Something like
image

@CommanderStorm
Copy link
Collaborator

Notify on all events

Notifying on all means storing all.
See #4500 why this is not a good idea for performance reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

6 participants