Wiki source code of Introduction

Last modified by Erik Bakker on 2024/09/03 09:57

Hide last authors
Erik Bakker 2.1 1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
Erik Bakker 9.1 4 In this introduction to the RCA Knowledge base we will describe a generic process that can be used by a support engineer to better, and hopefully faster, analyze support tickets that are coming in.
Erik Bakker 2.1 5
6 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 == 1. Situation ==
9
Erik Bakker 9.1 10 When a ticket comes in it is up to the Support Engineer to determine, once the ticket is accepted, what the cause of the problem described in the ticket. When looking at the context of eMagiz there is a predefined set of steps one can follow to understand the problem better and subsequently arrive at conclusions. In the remainder of this introduction we will describe this step by step approach as a written reminder of how to go about solving a support ticket.
Erik Bakker 2.1 11
12 == 2. Problem ==
13
Erik Bakker 9.1 14 A ticket related to an eMagiz model is registered and needs to be solved.
Erik Bakker 2.1 15
16 == 3. Analysis ==
17
Erik Bakker 9.1 18 === 3.1 Step by step approach ===
Erik Bakker 2.1 19
Erik Bakker 9.1 20 ==== 3.1.1 Question the client ====
21
Erik Bakker 13.1 22 Before you even open eMagiz the first task is to clarify the problem reported by the client. In this discussion, which can happen in person or digitally, the following questions will ensure you learn a lot from the context of the problem. Note that the initial clarification given by the client upon reporting the ticket can be sufficient to answer the questions below.
Erik Bakker 9.1 23
24 * Can you, as the reporter, shed light on what you think the problem is? Is there already information known to the client (i.e. error messages, logging) that will help you understand the problem.
25 * Has something changed in the weeks leading to when the problems occurred?
26 * Is the problem specific to a single flow (i.e. flow level) or does it appear generic (i.e. runtime level)?
27 * Is the flow/runtime running in the eMagiz cloud or on-premise? (or is it a mendix system)
28 * In what environment is the problem occurring?
29 * Can I get access to the model in which the problem is occuring?
30
31 ==== 3.1.2 Analyze problem in eMagiz ====
32
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
Erik Bakker 16.1 35 ===== 3.1.2.1 Flow level =====
36
Erik Bakker 11.1 37 In case of a **flow level** problem the following overviews are most interesting when analyzing the ticket:
Erik Bakker 9.1 38
Erik Bakker 10.1 39 * [[Dashboard>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message||target="blank"]]
Erik Bakker 9.1 40 ** 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.
Erik Bakker 12.1 41 * [[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.WebHome||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
Erik Bakker 11.1 42 ** 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.
Erik Bakker 13.1 43 * Logging
44 ** When the two approaches above don't get the clarity you want it is good to take a look at the logging within eMagiz. In here filter first on type Error and subsequently on type Warning (within the time frame of the reported problem) to see whether any logging can shed a light on the problem.
Erik Bakker 9.1 45
Erik Bakker 14.1 46 Should Manage not provide you the answers it becomes time to challenge the assumptions of the client on the problem. This can be done with the help of the Deploy phase ([[Compare Releases>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]], [[Start/Stop Flows>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]], [[Properties>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]) and Create ([[Flow Designer>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-flow-editor-basics||target="blank"]]). In these two phases you need to verify the following.
Erik Bakker 9.1 47
Erik Bakker 13.1 48 * Is the expected flow version running?
49 * Is the expected runtime running stable?
50 * Is a property value updated?
51 * Is there a configuration problem in the current flow version in Create that is also deployed?
52
53 With all this information you should be able to solve 99% of all the **flow** related support tickets.
54
Erik Bakker 16.1 55 ===== 3.1.2.2 Runtime level =====
56
Erik Bakker 15.1 57 In case of a **runtime level** problem the following overviews are most interesting when analyzing the ticket:
Erik Bakker 13.1 58
Erik Bakker 20.1 59 * [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
Erik Bakker 15.1 60 ** In here you can view statistics on runtime level. Here you can see whether a runtime is actually sending metrics and whether it is/was in trouble. This way you can easily see whether the runtime has a configuration or memory problem.
61 * Logging
62 ** Once you have identified that a runtime is/was in trouble you can search for corresponding Error or Warning logs on runtime level. These shed additional light on why the runtime is in problem.
63
Erik Bakker 16.1 64 Should Manage not provide you the answers it becomes time to challenge the assumptions of the client on the problem. This can be done with the help of the Deploy phase. In this phase you check on runtime level what the status of the runtime is. You can do this by accessing the context menu on runtime level and selecting the option "Details".
Erik Bakker 15.1 65
Erik Bakker 16.1 66 [[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-introduction--details-context-menu-deploy-architecture.png]]
Erik Bakker 2.1 67
Erik Bakker 16.1 68 Selecting this option will lead you to the "Status" tab in which you can see whether the runtime is running (or not) and for how long it is in the current state.
Erik Bakker 2.1 69
Erik Bakker 16.1 70 [[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-introduction--details-status-menu-deploy-architecture.png]]
Erik Bakker 2.1 71
Erik Bakker 16.1 72 With all this information you should be able to solve 95% of all the **flow** related support tickets.
Erik Bakker 2.1 73
Erik Bakker 16.1 74 {{info}}Should you be unable to resolve the problem with only information from eMagiz you can check, assuming you have access, additional information in AWS and Portainer. These are not discussed here any further as they are only accessible for a limited set of users.{{/info}}
Erik Bakker 2.1 75
Erik Bakker 16.1 76 == 4. Result ==
Erik Bakker 2.1 77
Erik Bakker 16.1 78 With the help of this structure and the specified RCA-knowledgebase entries you are able to solve the vast majority of problems on your own or with a little help.
Erik Bakker 2.1 79
Erik Bakker 17.1 80 * [[Configuration Issues>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.WebHome||target="blank"]]
Erik Bakker 16.1 81 * [[Cloud Issues>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-cloud-issues.WebHome||target="blank"]]
82 * [[Runtime Issues>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-runtime-issues.WebHome||target="blank"]]
Erik Bakker 2.1 83
Erik Bakker 18.1 84 == 5. Suggested Additional Readings ==
85
Erik Bakker 19.1 86 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
87 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
Erik Bakker 22.1 88 *** [[Flow Designer (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-flow-editor-basics||target="blank"]]
89 *** [[Compare Releases (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]]
90 *** [[Properties (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
91 *** [[Dashboard (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-determining-origin-of-error-message||target="blank"]]
92 *** [[Runtime Statistics (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
Erik Bakker 19.1 93 ** [[Crash Course Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.WebHome||target="blank"]]
Erik Bakker 22.1 94 *** [[Queue Statistics (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3||target="blank"]]
Erik Bakker 19.1 95 ** [[Crash Course Event Streaming (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.WebHome||target="blank"]]
Erik Bakker 22.1 96 *** [[Event Streaming Statistics (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Event Streaming.crashcourse-eventstreaming-managing-your-event-streaming-solution||target="blank"]]
Erik Bakker 19.1 97 * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
98 ** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]]
Erik Bakker 22.1 99 *** [[Start/Stop Flows (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]]
Erik Bakker 19.1 100 * [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
101 ** [[Advanced Monitoring (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.WebHome||target="blank"]]
Erik Bakker 22.1 102 *** [[HTTP Statistics (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-http-statistics.WebHome||target="blank"]]
Erik Bakker 21.1 103 * [[RCA (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?text=%22rca%22&f_type=DOCUMENT&f_space_facet=0%2FMain.&f_locale=en&f_locale=&f_locale=en&r=1||target="blank"]]
Erik Bakker 18.1 104 )))
105
Erik Bakker 2.1 106 (((
107 {{toc/}}
108 )))
109 {{/container}}
110 {{/container}}