Skip to content

Send notifications via webhook #841

Closed

Description

@rons4

Is there an existing issue for this?

  • I have searched the existing issues.

Describe the solution you'd like

It would be great to send notifications via email (SMTP) and webhook (HTTP Post). This would allow to integrate mobile alerting services like SIGNL4.

Integrating mobile alerting ensures users, e.g. on-call engineers, receive critical alerts even if not in front of the dashboard.

PS: I openen this issue here as discussed on Reddit ;-)

Is your feature request related to a problem?

No response

Activity

  1. abiteman commented on Jun 30, 2025

    @abiteman

    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.

  2. GyulyVGC commented on Jun 30, 2025

    @GyulyVGC
    Owner

    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.

  3. self-assigned this
    on Jun 30, 2025
  4. added this to the v1.4.1 milestone on Jun 30, 2025
  5. GyulyVGC commented on Jun 30, 2025

    @GyulyVGC
    Owner

    @all-contributors please add @rons4 for ideas.

  6. allcontributors commented on Jun 30, 2025

    @allcontributors
    Contributor

    @GyulyVGC

    I've put up a pull request to add @rons4! 🎉

  7. rons4 commented on Jul 1, 2025

    @rons4
    Author

    Hi @GyulyVGC, thanks and I usually see different levels:

    1. 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.

    2. 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.

    {
      "Host": {host}
      "Service": {service}
      "Traffic": {traffic}
    }
    

    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.

    1. 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.

  8. removed their assignment
    on Jul 1, 2025
  9. GyulyVGC commented on Jul 1, 2025

    @GyulyVGC
    Owner

    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.

  10. removed this from the v1.4.1 milestone on Jul 1, 2025
  11. rons4 commented on Jul 2, 2025

    @rons4
    Author

    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.

  12. GyulyVGC commented on Jul 6, 2025

    @GyulyVGC
    Owner

    I'll definitely give it a try.

  13. self-assigned this
    on Jul 9, 2025
  14. added this to the v1.4.1 milestone on Jul 9, 2025
  15. modified the milestones: v1.4.1, v1.4.2 on Aug 14, 2025
  16. GyulyVGC commented on Sep 9, 2025

    @GyulyVGC
    Owner

    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?

  17. rons4 commented on Sep 10, 2025

    @rons4
    Author

    Thanks, @GyulyVGC. Good point.

    I have seen three options with other tools:

    1. 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

    2. 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.

    3. 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.

  18. GyulyVGC commented on Sep 10, 2025

    @GyulyVGC
    Owner

    I will try with SIGNL4 and see how it looks like, thanks!

  19. rons4 commented on Sep 11, 2025

    @rons4
    Author

    Sounds great. Just let me know if you should need anything. I am happy to help.

  20. GyulyVGC commented on Sep 11, 2025

    @GyulyVGC
    Owner

    Thanks so much for your availability.
    I'll tag you once the PR is ready for a review!

  21. changed the title [-]Send notifications via email and webhook[/-] [+]Send notifications via webhook[/+] on Oct 10, 2025
  22. linked a pull request that will close this issueRemote notifications via webhook #991on Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature, request, or improvement

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions