Project

General

Profile

Feature #26693

Feature #23785: FreeNAS sending SNMP traps/notifications

Choice of alert systems not ideal for many users - add GSM and other options.

Added by Stilez y over 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Estimated time:
Severity:
Low Medium
Reason for Closing:
Not to be fixed
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

The current alert mechanisms (apart from email) are really geared to IT professionals and those purchasing commercial management/collaboration services of some kind.

When people use FreeNAS as a standalone home server or for a home lab or small office, most of the alert systems available (AWS, Slack...) just aren't appropriate choices, and several are also third party paid products.

Can we have a slightly wider list of options, catering to other FreeNAS/TrueNAS users?

  1. GSM notifications (FreeBSD supports GSM cards which can notify via SMS - useful if the alert is about connectivity or if internet links aren't available remotely)
  2. A feed URL on the internal web server - local devices (and also remote devices that are allowed in through the local firewall) could use this and small free tray feed clients are very easy to find for all platforms.
  3. Growl - has been popular in many quarters
  4. Some kind of standard push notifications suited to iPhone + Android clients

Related issues

Related to FreeNAS - Feature #26679: Add System -> Alerts for configuring alert frequencyDone

History

#1 Updated by Stilez y over 2 years ago

Also related: issue #26679 ("Granularity for alerts")

#2 Updated by Dru Lavigne over 2 years ago

  • Related to Feature #26679: Add System -> Alerts for configuring alert frequency added

#3 Updated by Dru Lavigne over 2 years ago

  • Assignee changed from Release Council to Marcelo Araujo

#4 Updated by William Grzybowski over 2 years ago

  • Assignee changed from Marcelo Araujo to Vladimir Vinogradenko

#5 Updated by Vladimir Vinogradenko over 2 years ago

  • Status changed from Unscreened to Screened
  • Parent task set to #23785

#6 Updated by Dru Lavigne over 2 years ago

  • Target version set to 11.2-BETA1

#7 Updated by Stilez y over 2 years ago

Note regarding feed URL - can this option have a setting for (port number) + either (interfaces/IPs)? So that one can expose the feed in a way that's completely isolated from the main GUI.

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore over 2 years ago

  • Target version changed from 11.2-BETA1 to 11.3

#9 Avatar?id=14398&size=24x24 Updated by Kris Moore about 2 years ago

  • Status changed from Screened to Not Started

#10 Avatar?id=13649&size=24x24 Updated by Ben Gadd almost 2 years ago

  • Target version changed from 11.3 to Backlog

#11 Updated by Vladimir Vinogradenko almost 2 years ago

  • Severity set to Low Medium

#12 Updated by Dru Lavigne about 1 year ago

  • Status changed from Not Started to Closed
  • Target version changed from Backlog to N/A
  • Reason for Closing set to Not to be fixed

Stilez: we have decided to pass on this feature at this time in order to devote resources to other features. However, PRs are always welcome :-)

#13 Updated by Stilez y about 1 year ago

That's actually appreciated - a fair, helpful honest explanation, much better than just letting it linger.

A few quick questions on this, to help anyone (or myself) who takes this on:

  • Are alert methods accessed via some kind of pluggable/standardised internal API, or standard dispatcher, which would make it easy to add new methods either to the base code or as plugins of some kind?
  • If so, where would one look/start at? (i.e., quick tips of the key parts/func defs in the codebase)?
  • And would it be better to add them as base code, or optional user-instalable plugins/modules of some kind?

If they aren't already instantiated/configured/called via some standard method/layer/dispatcher:

  1. How easy would it be to wrap existing alert calls and make them so (even if just via a wrapper/shim for now)?
  2. What would someone have to do, to do this?
  3. Is there any point submitting that as a request (i.e., moving existing alert method calls to a standardised call structure), since that'll greatly help with anyone doing future work on alerts? Or would that be likely to be closed/v. low priority too?

#14 Updated by Vladimir Vinogradenko about 1 year ago

You can just use any of this files as an example to create another one https://github.com/freenas/freenas/blob/freenas/11.2-stable/src/middlewared/middlewared/alert/service

You'll be able to use new alert service via API 2.0 after putting new file in that directory

UI forms are here https://github.com/freenas/webui/blob/freenas/11.2-stable/src/app/pages/system/alertservice/alert-service/alert-service.component.ts

Also available in: Atom PDF