Changes for page AWS Burst Credits Issue

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-AWS Birst Credits Issue
	1	+AWS Burst Credits Issue

Content

...	...	@@ -5,11 +5,11 @@
5	5
6	6	== 1. Situation ==
7	7
8		-When developing your integration solution with the eMagiz platform and running your solution in the AWS cloud, it can happen that your allotted Birst credits on the EFS are depleting. When this happens, you need to analyze the problem, preferably before the credits run out. If you do not do this in time, your interaction with EFS defaults to a baseline that is 'too slow for you (as your EFS burst credits are depleting).
	8	+When developing your integration solution with the eMagiz platform and running your solution in the AWS cloud, it can happen that your allotted Burst credits on the EFS are depleting. When this happens, you need to analyze the problem, preferably before the credits run out. If you do not do this in time, your interaction with EFS defaults to a baseline that is 'too slow for you (as your EFS burst credits are depleting).
9	9
10	10	== 2. Problem ==
11	11
12		-The problem, in this case, was that a loop of messages was created, generating incorrect data that was processed by the system. As a result, much interaction with EFS was triggered, leading to the depletion of Birst credits.
	12	+The problem, in this case, was that a loop of messages was created, generating incorrect data that was processed by the system. As a result, much interaction with EFS was triggered, leading to the depletion of Burst credits.
13	13
14	14	== 3. Analysis ==
15	15
...	...	@@ -32,8 +32,8 @@
32	32	* Bursting throughput
33	33	** This option gives you a balance (number of credits) that you can use to increase your bandwidth when needed temporarily. This is the standard method when using eMagiz. The larger the difference between the baseline and what you use, the more burst credits will go down (or up). Once the actual usage is higher compared to the baseline the burst credits will go down. Vice versa, the burst credits will increase when the actual usage is lower.
34	34	** For more information, see:
35		-*** https://aws.amazon.com/premiumsupport/knowledge-center/efs-burst-credits/
36		-*** https://docs.aws.amazon.com/efs/latest/ug/performance.html#bursting
	35	+*** [[EFS Burst credits explained>>https://aws.amazon.com/premiumsupport/knowledge-center/efs-burst-credits/||target="blank"]]
	36	+*** [[Bursting>>https://docs.aws.amazon.com/efs/latest/ug/performance.html#bursting||target="blank"]]
37	37
38	38	{{warning}}The moment your credit balance is down to zero your maximum throughput equals the throughput as defined in the baseline{{/warning}}
39	39
...	...	@@ -72,13 +72,15 @@
72	72	[[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-aws-burst-credits-development-burst-impact-on-birst-credit-balance.png]]
73	73
74	74	* Based on the above example, a bandwidth of 1.5 MiB/s should be sufficient to stabilize the Burst balance.
75		-* More information on the calculation can be found here: https://docs.aws.amazon.com/efs/latest/ug/monitoring-metric-math.html en https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/using-metric-math.html
	75	+* More information on the calculation can be found here:
	76	+ ** [[Metric math explained>>https://docs.aws.amazon.com/efs/latest/ug/monitoring-metric-math.html||target="blank"]]
	77	+ ** [[Using metric math>>https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/using-metric-math.html||target="blank"]]
76	76
77	77	=== 3.4 EFS Burst Performance & Calculation ===
78	78
79	79	In case of a structural problem with the throughput being used, additional investigation is warranted. There are several causes for this:
80	80	* Excessive logging -> You can check this under CloudWatch -> "Log Groups". By clicking on the cogwheel and selecting the option "Stored bytes" AWS will show you the size of each log. If the number you see seems unexpectedly large, you can dig deeper into the log to see which logs could explain this behavior.
81		-* Excessive 'metadata' -> In eMagiz, you can build your solutions how you like to develop them. There are, however, also constructions that take many steps to finish. As a result, much 'metadata' could be added to your message (such as the channels you have traversed). It can even grow subsequently bigger as your actual message. Read this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-impact-message-history-on-message-size.WebHome||target="blank"]] for context and possible solutions to fix the issue.
	83	+* Excessive 'metadata' -> In eMagiz, you can build your solutions how you like to develop them. There are, however, also constructions that take many steps to finish. As a result, much 'metadata' could be added to your message (such as the channels you have traversed). It can even grow subsequently bigger as your actual message. Read this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-impact-message-history-on-message-size||target="blank"]] for context and possible solutions to fix the issue.
82	82	* Repeating messages -> Input is not cleaned up, which means that messages keep coming in. This, in turn, increases traffic and results in a higher throughput on EFS. If this is unnecessary, you can change it to save much bandwidth.
83	83	* A high number of messages compared to file size -> This is something you can only help with as a user. In this case, you are in a situation with much data traffic between various systems. You should either increase the file size or activate provisioned throughput to solve this.
84	84