Skip to Content

Changes for page Monitoring

Last modified by Erik Bakker on 2024/09/24 16:24
From version 36.1
edited by eMagiz
on 2022/09/05 10:47
Change comment: There is no comment for this version
To version 33.1
edited by Erik Bakker
on 2022/06/23 16:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Monitoring
1 +Advanced monitoring
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,9 +1,8 @@
1 -{{velocity}}
2 -#set ($discard = $xwiki.ssx.use('Main.Extensions.ContainerSizingCoursePage.WebHome'))
3 -{{/velocity}}
1 +In this course, we will look at how you can successfully monitor your complete integration data model with the help of elements from the eMagiz Portal. At first, we will take a look at retesting functionality based on conclusions drawn from eMagiz. Furthermore, this course will focus on monitoring options when running (part of) your messaging solution on-premise. When running on-premise, you can access the logs on disk. These logs can sometimes aid in determining why there are troubles with setting up the proper connection between the on-premise runtime and the JMS instance running in the cloud.
4 4  
5 -{{container}}{{container layoutStyle="columns"}}(((In this course, we will look at how you can successfully monitor your complete integration data model with the help of elements from the eMagiz Portal. At first, we will take a look at retesting functionality based on conclusions drawn from eMagiz. Furthermore, this course will focus on monitoring options when running (part of) your messaging solution on-premise. When running on-premise, you can access the logs on disk. These logs can sometimes aid in determining why there are troubles with setting up the proper connection between the on-premise runtime and the JMS instance running in the cloud.)))((({{html}}<div class="strip__attribute" style="text-align:center"><table><tr><td><img class="strip__attribute-icon strip__attribute-icon--duration" src="/bin/download/Main/Images/General/WebHome/icon-duration32.svg"/></td></tr><tr><td><div class="strip__attribute-label">25-30 minutes</div></td></tr></table></div>{{/html}}))){{/container}}{{/container}}
3 +* **Total time:** between 15 and 25 minutes
6 6  
5 +
7 7  (% style="border-color:#10137e" %)
8 8  ----
9 9  {{html}}
... ... @@ -12,10 +12,10 @@
12 12   <main class="master">
13 13   <ul class="strip-container">
14 14   <li class="strip">
15 - <a href="/bin/view/Main/eMagiz%20Academy/Microlearnings/Advanced%20Level/Advanced%20monitoring/intermediate-active-monitoring-determining-origin-of-log-entry" class="strip__link">
14 + <a href="/bin/view/Main/eMagiz%20Academy/Microlearnings/Advanced%20Level/Advanced%20monitoring/advanced-active-monitoring-determining-cause-of-log-entry" class="strip__link">
16 16   <label for="" class="strip__label">
17 17   <span>320</span>
18 - Management of log entries
17 + Determining cause of log entry
19 19   </label>
20 20   <div class="strip__attribute">
21 21   <img class="strip__attribute-icon strip__attribute-icon--duration" src="/bin/download/Main/Images/General/WebHome/icon-duration32.svg"/>
... ... @@ -31,11 +31,11 @@
31 31   </div>
32 32   </a>
33 33   </li>
34 - <li class="strip">
35 - <a href="/bin/view/Main/eMagiz%20Academy/Microlearnings/Advanced%20Level/Advanced%20monitoring/advanced-active-monitoring-determining-cause-of-log-entry" class="strip__link">
33 + <li class="strip">
34 + <a href="/bin/view/Main/eMagiz%20Academy/Microlearnings/Advanced%20Level/Advanced%20monitoring/advanced-active-monitoring-preventive-action-based-on-error-message" class="strip__link">
36 36   <label for="" class="strip__label">
37 37   <span>320</span>
38 - Determining root cause of log entries
37 + Preventive actions based on error message
39 39   </label>
40 40   <div class="strip__attribute">
41 41   <img class="strip__attribute-icon strip__attribute-icon--duration" src="/bin/download/Main/Images/General/WebHome/icon-duration32.svg"/>