| 2011-07-12 09:18:48 |
Muharem Hrnjadovic |
bug |
|
|
added bug |
| 2011-07-12 09:18:59 |
Muharem Hrnjadovic |
tags |
|
error-feedback messaging |
|
| 2011-07-15 10:05:58 |
Muharem Hrnjadovic |
tags |
error-feedback messaging |
log-consolidation messaging |
|
| 2011-07-15 10:06:10 |
Muharem Hrnjadovic |
openquake: status |
New |
Confirmed |
|
| 2011-07-15 10:06:13 |
Muharem Hrnjadovic |
openquake: importance |
Undecided |
Medium |
|
| 2011-07-15 10:06:15 |
Muharem Hrnjadovic |
openquake: milestone |
|
0.4.2 |
|
| 2011-07-15 10:50:31 |
Muharem Hrnjadovic |
tags |
log-consolidation messaging |
job-supervision log-consolidation messaging |
|
| 2011-07-15 10:51:03 |
Muharem Hrnjadovic |
summary |
RabbitMQ backend for logging implementation must be configurable |
RabbitMQ backend for logging must transport error logs |
|
| 2011-07-15 10:53:15 |
Muharem Hrnjadovic |
description |
It should e.g. be configurable which logging severity levels should be transported via RabbitMQ, which brokers, vhosts, exchanges and queues to use etc. |
The job supervisors will detect failures based on log.[critical|fatal|error].<jobid> messages i.e. the log records for these severities must be pumped through the 'signalling' topic exchange. The others are optional and we should consider having a switch for turning them off. |
|
| 2011-07-21 14:21:55 |
John Tarter |
openquake: milestone |
0.4.2 |
0.4.3 |
|
| 2011-09-06 16:45:47 |
John Tarter |
openquake: milestone |
0.4.3 |
0.4.4 |
|
| 2011-09-08 12:27:22 |
Muharem Hrnjadovic |
openquake: status |
Confirmed |
Fix Released |
|
| 2011-09-08 15:02:50 |
John Tarter |
openquake: assignee |
|
Muharem Hrnjadovic (al-maisan) |
|
