Complete OQ log records need to be stored in central place
Bug #809222 reported by
Muharem Hrnjadovic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Medium
|
Gabriele Favalessa | ||
Bug Description
The idea is to have a message consumer process subscribed to all log records and dumping the latter to the standard python logging facility.
| tags: | added: error-feedback |
| tags: | added: database nosql |
| summary: |
- Log records containing errors/failure data must be persisted + Log records containing errors/failure data must be persisted in a + central place |
| tags: | removed: database |
| description: | updated |
| summary: |
- Log records containing errors/failure data must be persisted in a + Complete OQ log records for a configurable period need to be stored in central place |
| summary: |
- Complete OQ log records for a configurable period need to be stored in - central place + Complete OQ log records need to be stored in central place |
| tags: |
added: log-consolidation sys-quality removed: error-feedback nosql |
| Changed in openquake: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 0.4.2 |
| description: | updated |
| description: | updated |
| Changed in openquake: | |
| milestone: | 0.4.2 → 0.4.3 |
| tags: |
added: devop removed: sys-quality |
| Changed in openquake: | |
| assignee: | nobody → Gabriele Favalessa (favalex) |
| status: | Confirmed → In Progress |
| description: | updated |
| description: | updated |
Revision history for this message
| Gabriele Favalessa (favalex) wrote | #1 |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Pull request https:/