[QAARQ-37] Confirmation of publish in public instances Created: 04/May/20 Updated: 05/May/20 |
|
| Status: | Open |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Low |
| Reporter: | Richard Gange | Assignee: | Andrew Warinner |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| 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)
|
||||
| Date of First Response: | |||||
| Description |
|
Configuring activation in the Assets app is successful (the documentation has been updated). However there are no changes observed in the Queued messages graph. There is activity in the Message rates graph. It would be good to have at least on INFO statement in the public log to confirm the publication actually happened in case there is a need to track down errors. |
| Comments |
| Comment by Andrew Warinner [ 04/May/20 ] |
|
Hi Rich, This may be an artifact of the RMQ dashboard, rather than the RMQ module itself. The dashboard may be not be seeing any queued messages when it is periodically refreshed. I see this all the time on a local RMQ server when using auto-ack for messages. The RMQ publishing module doesn't use auto-ack, it uses manual ack, but if it is fast enough, you may not see spikes in the queued messages graph if the messages are consumed quickly enough. Also, if there was some kind of problem with the publication, then the messages should stay queued because of the manual ack. AW |
| Comment by Richard Gange [ 04/May/20 ] |
|
Ok, that makes sense. I have not seen that. It might be good to have some confirmation in the public log for every publication at the INFO level. I will repurpose the ticket. |