[
https://issues.apache.org/jira/browse/OOZIE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryota Egashira updated OOZIE-929:
---------------------------------
Description:
Oozie customers have requirements for monitoring, including notification on Job
Status and SLA. Notifications can be sent in the form of email or using JMS
(message bus) where pub-sub messaging model is applied.
This is parent JIRA for design and implementation of Job and SLA notification,
where each individual work is defined as sub-task.
Architectural design has been discussed in the community, and all documents are
attached here.
was:
Currently for each notification, oozie uses an http connection to send a
notification. Oozie could use a pub-sub model and a JMS message bus.
1. There are a few options for the topic. It could be user generated, although
this would allow a lot of topics and inconsistent naming. It could be per job
so users could subscribe to see the notifications of certain jobs. It could be
done per user.
2. Ways to handle the large number of notifications since one notification
could go to many subscribers. The payload of the notifications should be
considered. Should it include everything about the action or should it only
include important things like action id, action status, and time?
> Notifications in Oozie
> ----------------------
>
> Key: OOZIE-929
> URL: https://issues.apache.org/jira/browse/OOZIE-929
> Project: Oozie
> Issue Type: New Feature
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Attachments: DesignConsiderations.txt, OOZIE-929.patch,
> OozieMonitoring-929-1244.pptx
>
>
> Oozie customers have requirements for monitoring, including notification on
> Job Status and SLA. Notifications can be sent in the form of email or using
> JMS (message bus) where pub-sub messaging model is applied.
> This is parent JIRA for design and implementation of Job and SLA
> notification, where each individual work is defined as sub-task.
> Architectural design has been discussed in the community, and all documents
> are attached here.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
