You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you @rons4 for the amazing idea 🙏
Since you surely have more expertise than me in this field... what do you suggest supporting as a transmission method? I see you mention both SMTP and HTTP, but I'm wondering which once of the two has more benefits. Or maybe if there's another kind of protocol that I could use 🤔
For what concerns @abiteman's suggestion to use apprise... I'd prefer to use a strategy that's lightweight, possibly zero-dependencies.
Hi @GyulyVGC, thanks and I usually see different levels:
Simple email notifications
Ability to send simple emails in case an issue has been detected.
In this case the user can configure the SMTP server and email address.
Good and straightforward for all kinds of integrations with notification or alerting services.
Email and Webhook with parameters
Additionally to the above users can also configure to send HTTP Post requests.
The texts for the email or HTTP Post body support placeholders, e.g.
You can also allow to send notifications in case of an issue and in case of an OK state in order to allow closing the alert again.
Support specific notification channels
Additionally to the above support dedicated notification and alerting services like SMS, SIGNL4, Pagerduty, etc.
My recommendation would be to start simple ;-) I hope this helps.
After more carefully thinking about this, I believe it requires a bit more investigation from my side before an actual implementation.
I feel like leaving to the users the burden to setup an SMTP server is slightly against the simplicity principles of the app, so I'll have to figure out a way to do this in a more plug-and-play manner.
Hi @GyulyVGC, yea, I guess that makes sense. Entering SMTP server details not not exactly plug-and-play. Maybe a simple HTTP Post webhook would still be nice. Users can just enter the URL and can thus communicate with alerting services, or no-code platforms.
Hey @rons4 I'm getting closer to start with the implementation of this feature and I have a couple things I'd like to ask you.
I guess that the ideal format for the body of the HTTP Post is a JSON structure where I can set different fields describing the details of the notification.
So my doubt is: given that the body of our Post will be a custom defined structure, how can we be sure that the receiving web server interprets it correctly? How can it extract and show meaningful information without knowing the details of the JSON object? Should we assume that it's configured to read the specific fields in the JSON as defined by Sniffnet?
You send the JSON format your way and the alerting or notification too needs to digest it. In order to be most flexible and compatible SIGNL4 uses this approach and tries to interpret the JSON and display the alert in a nice way. Here is the webhook description: https://docs.signl4.com/integrations/webhook/webhook.html
The notification / alerting solution requires a special format. This requires the tool to send this format, i.e. to assemble dynamic JSON and HTTP headers.
You want to connect a tool that sends one format with an alerting / notification solution that supports a different format. In this case a "translator" is required, e.g. a no-code tool like n8n, Make, or Zapier.
Of course, is is always a question of effort, benefits and priorities, so stating with 1. might be a good first step.
Activity
abiteman commentedon Jun 30, 2025
Consider utilizing apprise, it's a great way to support a ton of different notification services that can be built right in to the app.
GyulyVGC commentedon Jun 30, 2025
Thank you @rons4 for the amazing idea 🙏
Since you surely have more expertise than me in this field... what do you suggest supporting as a transmission method? I see you mention both SMTP and HTTP, but I'm wondering which once of the two has more benefits. Or maybe if there's another kind of protocol that I could use 🤔
For what concerns @abiteman's suggestion to use apprise... I'd prefer to use a strategy that's lightweight, possibly zero-dependencies.
GyulyVGC commentedon Jun 30, 2025
@all-contributors please add @rons4 for ideas.
allcontributors commentedon Jun 30, 2025
@GyulyVGC
I've put up a pull request to add @rons4! 🎉
rons4 commentedon Jul 1, 2025
Hi @GyulyVGC, thanks and I usually see different levels:
Simple email notifications
Ability to send simple emails in case an issue has been detected.
In this case the user can configure the SMTP server and email address.
Good and straightforward for all kinds of integrations with notification or alerting services.
Email and Webhook with parameters
Additionally to the above users can also configure to send HTTP Post requests.
The texts for the email or HTTP Post body support placeholders, e.g.
You can also allow to send notifications in case of an issue and in case of an OK state in order to allow closing the alert again.
Additionally to the above support dedicated notification and alerting services like SMS, SIGNL4, Pagerduty, etc.
My recommendation would be to start simple ;-) I hope this helps.
GyulyVGC commentedon Jul 1, 2025
Thanks for the details!
After more carefully thinking about this, I believe it requires a bit more investigation from my side before an actual implementation.
I feel like leaving to the users the burden to setup an SMTP server is slightly against the simplicity principles of the app, so I'll have to figure out a way to do this in a more plug-and-play manner.
rons4 commentedon Jul 2, 2025
Hi @GyulyVGC, yea, I guess that makes sense. Entering SMTP server details not not exactly plug-and-play. Maybe a simple HTTP Post webhook would still be nice. Users can just enter the URL and can thus communicate with alerting services, or no-code platforms.
GyulyVGC commentedon Jul 6, 2025
I'll definitely give it a try.
GyulyVGC commentedon Sep 9, 2025
Hey @rons4 I'm getting closer to start with the implementation of this feature and I have a couple things I'd like to ask you.
I guess that the ideal format for the body of the HTTP Post is a JSON structure where I can set different fields describing the details of the notification.
So my doubt is: given that the body of our Post will be a custom defined structure, how can we be sure that the receiving web server interprets it correctly? How can it extract and show meaningful information without knowing the details of the JSON object? Should we assume that it's configured to read the specific fields in the JSON as defined by Sniffnet?
rons4 commentedon Sep 10, 2025
Thanks, @GyulyVGC. Good point.
I have seen three options with other tools:
You send the JSON format your way and the alerting or notification too needs to digest it. In order to be most flexible and compatible SIGNL4 uses this approach and tries to interpret the JSON and display the alert in a nice way. Here is the webhook description:
https://docs.signl4.com/integrations/webhook/webhook.html
The notification / alerting solution requires a special format. This requires the tool to send this format, i.e. to assemble dynamic JSON and HTTP headers.
You want to connect a tool that sends one format with an alerting / notification solution that supports a different format. In this case a "translator" is required, e.g. a no-code tool like n8n, Make, or Zapier.
Of course, is is always a question of effort, benefits and priorities, so stating with 1. might be a good first step.
I hope this makes sense.
GyulyVGC commentedon Sep 10, 2025
I will try with SIGNL4 and see how it looks like, thanks!
rons4 commentedon Sep 11, 2025
Sounds great. Just let me know if you should need anything. I am happy to help.
GyulyVGC commentedon Sep 11, 2025
Thanks so much for your availability.
I'll tag you once the PR is ready for a review!
[-]Send notifications via email and webhook[/-][+]Send notifications via webhook[/+]