Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Excerpt

Unresolved issues for alarms

Old history on (un)resolved issues

How much does the Alarm Service cover?

  1. only alarms sent as alarm messages YES
  2. above and check that different parts of system is alive, fx by ping NO (done externally via getStatus)
  3. above and surveillance of queues for irregularities and/or messages with errors NO (done in monitoring Service which can raise alarm)
  4. above and surveillance of file exchange protocol??? NO (done in monitoring Service which can raise alarm)
  5. more???? No (keep it simple)

Remember

  • Check notifications service part of strategy project DONE
  • The alarm queue should be a Durable topic to ensure alarms aren't lost during client/service restarts.

When should alarms be generated

  • Should message receivers generate alarms when unexpected messages are received. Note that the corrupt message might be an alarm, which might even be generated by the receiver itself. This will cause an alarm chain reaction.
simple
Child pages (Children Display)
depth3
styleh3
excerpttrue
excerptType
Jira Issues
columnstype,key,summary,status,fixversion
width500px
titleUnresolved issues
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+BITMAG+AND+resolution+%3D+Unresolved+AND+component+%3D+Alarms+ORDER+BY+priority+DESC&tempMax=1000