[QAARQ-23] Improve activation logging entries Created: 24/Jul/18 Updated: 05/Jun/19 |
|
| Status: | Open |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Description |
|
Using the standard Magnolia activation, for the activate and deactivate actions this entries are logged:
Using RabbitMQ, this entries are logged:
Would be great to have this original information with RabbitMQ too. Often, we need to find out "who" activated "when" "what". Having ~2'000 authors, we appreciate this level of log details. |
| Comments |
| Comment by Richard Gange [ 27/Jul/18 ] |
|
We have to put this on hold until |