On Tue, Jan 24, 2017 at 6:55 AM, Ewoud Kohl van Wijngaarden <
[email protected]> wrote:
> On Tue, Jan 24, 2017 at 11:32:39AM +0100, Daniel Lobato Garcia wrote:
> > On 01/23, Tom McKay wrote:
> > > + Every notification we add to this system should be required to have a
> > > unique ID based on where it is in the code. This ID could be leveraged
> for
> > > access insights, docs, etc. (Maybe this is already the case?)
> >
> > It's the case - the notification blueprint comes with a 'subject' field
> > which is meant for specifying which object does this notification 'stem
> > from'
>
> I think Tom means a unique code for every notification type, like the
> smart proxy has error codes. To me a subject sounds like the subject of
> an email.
>
>
Yes, I mean unique code for each message type ("XYZ-1234 Capsule '
mycapsule.example.com' is offline"). I could then choose to include/exclude
these error messages from the UI. Perhaps I exclude from the UI and add
that message type to the list of email notifications.
It's great we have a little UI widget but the larger picture of
notifications and their delivery would be good to address too. Unique
message type/id would be an incremental step towards that.
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
