Wiki source code of Queue browser
Version 15.1 by Eva Torken on 2023/08/10 16:38
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
7.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
1.1 | 2 | |
| |
13.1 | 3 | {{warning}} |
| 4 | Please note that this microlearning is for the new monitoring stack only. | ||
| 5 | {{/warning}} | ||
| |
1.1 | 6 | |
| |
14.1 | 7 | In this microlearning, we will focus on the queue browser functionality. This new feature within our 3rd generation runtime allows you to view data flowing through your system. On top of that, it enables you to wiretap information for analysis purposes and even delete messages that should not be in a specific queue. |
| |
13.1 | 8 | |
| |
7.1 | 9 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 10 | |
| 11 | == 1. Prerequisites == | ||
| 12 | |||
| 13 | * Basic knowledge of the eMagiz platform | ||
| 14 | * Understanding of the flow testing functionality | ||
| 15 | |||
| 16 | == 2. Key concepts == | ||
| 17 | |||
| |
14.1 | 18 | This microlearning centers around the queue browser. |
| |
1.1 | 19 | |
| |
14.1 | 20 | * The queue browser can be used to view data on the queue |
| 21 | * The queue browser can be used to wiretap a queue to see all future messages (in the next five minutes) | ||
| 22 | * Message payloads above 100KB are not shown | ||
| 23 | * The queue browser allows you to delete one (or all) message(s) from the queue | ||
| |
1.1 | 24 | |
| |
14.1 | 25 | == 3. Queue browser == |
| |
1.1 | 26 | |
| |
14.1 | 27 | To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests. |
| |
1.1 | 28 | |
| |
14.1 | 29 | To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button. |
| |
1.1 | 30 | |
| |
15.1 | 31 | [[image:Main.Images.Release Blog.WebHome@queue-browser-overview.png]] |
| |
1.1 | 32 | |
| |
15.1 | 33 | 190-release-blog--queue-browser-overview.png |
| 34 | |||
| |
14.1 | 35 | After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that have passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal. |
| |
1.1 | 36 | |
| |
14.1 | 37 | * Delete the message from the queue (Explore option) |
| 38 | ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue. | ||
| 39 | * Clear message from the wiretap queue (Wiretap option) | ||
| 40 | ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview, so it does not clutter the view anymore | ||
| 41 | * Refresh messages list (both options) | ||
| 42 | ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first | ||
| 43 | * Save as test message | ||
| 44 | ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality. | ||
| 45 | * Download | ||
| 46 | ** By pressing this button, you can download the message and use it outside of the tooling should that be needed. | ||
| |
1.1 | 47 | |
| |
14.1 | 48 | [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] |
| |
1.1 | 49 | |
| |
14.1 | 50 | [[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]] |
| |
1.1 | 51 | |
| |
14.1 | 52 | {{info}} |
| 53 | The following restrictions apply to this functionality: | ||
| 54 | * Message payloads above 100KB are not shown in the queue browser as they constitute a "large message." | ||
| 55 | * The wiretap functionality works for five minutes, during which you can use the refresh button to see new messages coming in. | ||
| 56 | ** After five minutes, the wiretap functionality will be shut down automatically underwater. | ||
| 57 | ** To see new messages after five minutes, you must access the wiretap functionality from scratch. | ||
| 58 | {{/info}} | ||
| |
1.1 | 59 | |
| 60 | == 5. Key takeaways == | ||
| 61 | |||
| |
14.1 | 62 | * The queue browser can be used to view data on the queue |
| 63 | * The queue browser can be used to wiretap a queue to see all future messages (in the next five minutes) | ||
| 64 | * Message payloads in excess of 100KB are not shown | ||
| 65 | * The queue browser allows you to delete one (or all) message(s) from the queue | ||
| |
1.1 | 66 | |
| 67 | == 6. Suggested Additional Readings == | ||
| 68 | |||
| |
14.1 | 69 | If you are interested in this topic and want more information, please read the help texts in eMagiz. |
| |
1.1 | 70 | |
| 71 | |||
| |
7.1 | 72 | )))((({{toc/}}))){{/container}}{{/container}} |