Inbound webhook passive/heartbeat monitoring #1895

Closed
opened 2026-04-05 16:38:05 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @czb-ccoustier on 6/21/2023

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

We already have monitoring system internally that ping devices and send alerts when devices go down. It is redundant to have to setup the monitor in two places. With a passive monitor, OneUptime will be setup to take heartbeats from internal monitoring and any changes to devices only need to be updated in monitoring. The heartbeat to OneUptime doesn't change.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Have a configurable inbound/passive option for a component. Either accept inbound email alerts to each component to change status or accept a webhook for each component to change status. Another option is receiving a webhook at a configurable interval to maintain a online status, then if the heartbeat stops the component changes to offline. Also, vice versa, the option to have a device show online by default, then if it begins receiving webhooks it changes to offline until the heartbeat stops.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

The internal Docker probe goes a long way to make this feature almost unnecessary but the issue is having to setup monitors both on internal monitoring and in OneUptime.

Additional context
Add any other context or screenshots about the feature request here.

Check out other uptime monitor or status page product features related to "passive" or "heartbeat" or "cron" monitoring for similar ideas.

*Originally created by @czb-ccoustier on 6/21/2023* **Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] We already have monitoring system internally that ping devices and send alerts when devices go down. It is redundant to have to setup the monitor in two places. With a passive monitor, OneUptime will be setup to take heartbeats from internal monitoring and any changes to devices only need to be updated in monitoring. The heartbeat to OneUptime doesn't change. **Describe the solution you'd like** A clear and concise description of what you want to happen. Have a configurable inbound/passive option for a component. Either accept inbound email alerts to each component to change status or accept a webhook for each component to change status. Another option is receiving a webhook at a configurable interval to maintain a online status, then if the heartbeat stops the component changes to offline. Also, vice versa, the option to have a device show online by default, then if it begins receiving webhooks it changes to offline until the heartbeat stops. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. The internal Docker probe goes a long way to make this feature almost unnecessary but the issue is having to setup monitors both on internal monitoring and in OneUptime. **Additional context** Add any other context or screenshots about the feature request here. Check out other uptime monitor or status page product features related to "passive" or "heartbeat" or "cron" monitoring for similar ideas.
MrUnknownDE added the enhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancementenhancement labels 2026-04-05 16:38:11 +02:00
Sign in to join this conversation.
No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1895