Skip to Content

Changes for page Introduction

Last modified by Erik Bakker on 2024/09/03 09:57
From version 9.1
edited by Erik Bakker
on 2024/02/09 08:33
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2024/02/09 08:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,10 +32,12 @@
32 32  
33 33  Now that we have clarity on what we need to investigate and what the apparent problem is it becomes time to log in to eMagiz (my.emagiz.com) and open the model in question. With the information gathered in the first step you navigate to the Manage phase of eMagiz and select the environment in which the problem is occurring (mainly Production). In the Manage phase we have a lot of options at our disposal that will help us zoom in on the problem.
34 34  
35 -In case of a flow level problem the following overviews are most interesting when analyzing the ticket:
35 +In case of a **flow level** problem the following overviews are most interesting when analyzing the ticket:
36 36  
37 -* [[Dashboard>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message.WebHome||target="blank"]]
37 +* [[Dashboard>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message||target="blank"]]
38 38  ** In here you can view the error messages on flow level. This way you can easily see whether there are any errors in the reported flow or any flow that is related.
39 +* [[Queue>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3||target="blank"]]/[[HTTP>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-http-statistics||target="blank"]]/[[Event Streaming>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-managing-your-event-streaming-solution||target="blank"]] Statistics
40 +** In here you can view (depending on the pattern) whether messages actually ended up in a specific part of the process. When starting at the end of the process you can work your way back to the starting point of the process to see where the message broke down and if it even reached eMagiz in the first place.
39 39  
40 40  
41 41  First, you should check the assumptions of the person coming to you with a ticket. This is for both the Create and the Deploy phase of eMagiz. In Deploy, you check which version of a flow is running and whether this matches the client's expectations. Once you have established the correct flow version, it could happen that what is running is not what a user expected. The first step is to eliminate this mismatch.